I got a comment from someone from the Oracle team that works on the JDev Modeler on my past post. I was just going to post another comment, but hey, since I actually got some attention on my lame little blog, it probably deserves a full post.
Dai responded and was wondering what was giving me problems with generating from JDev. First of all, I have to say that I'm totally flattered that he read the post and responded -- especially since I was just whining into the Black Hole of the Internet.
First, let me say that I'm totally flattered that you read my whining -- "I'm not worthy..." The JDev Modeler ROCKS.
Here's the trouble that I end up having with the generating (in version 11.1.1.0.0).
I have to choose between 'CREATE, REPLACE or ALTER.' Thus, if I've created a table and made a change to a different table, I have to generate them separately. I'd prefer that it check the connection and generate a delta. Actually, this has been my only frustration. And, if I were working on one table at a time, it wouldn't be a big deal. Yesterday, I was attempting to do just that -- create foreign keys to two existing tables, alter some other existing tables and create several new ones. Basically, I pulled in a few tables into a database diagram, made some changes and enhancements and tried to implement them. What I ended up doing was dropping the two tables that I meant to create foreign keys to and then failing to create the full set of objects. Happily, this was in Dev.
Which brings me to one of my FAVORITE features in JDev Modeler. I love that it generates the sql script. However, I would prefer to get the script always -- even when it fails to run. That way, I can look at the script and fix the script. The reason that this is my favorite feature is that I love the point and click way of rolling out changes -- but only in Development. For Production, it should be from a script.
In fact, this is one of my favorite features in SQLDeveloper as well. They have been very good to (almost) always providing a way to see a script of any change that you are making through the UI. This is a fantastic feature. As I've mentioned, i feel strongly that the script is the only way to roll the code into test and production.
At this point, I should probably confess that I've spent a few years developing with Designer. So, I was spoiled by being able to point the generator at a database connection, have it generate a delta script WITHOUT applying it, then I could go apply and test the script. Nice feature.
But again, as a former Designer user, I LOVE the JDev er. Don't tell the SQLDeveloper er team, but I like the JDev version better. Yes, it does less. However, I love that it will create a sequence and trigger for a Primary Key column with the click of a button. That's just ONE example of how the JDev Modeler is more usable. Another confession -- I stopped using SQLDeveloper er once I found out that they were going to charge for it (and since I knew that JDev already had one that rocks for free). I've been a Contractor several times and I find that it pays to be able to use as many free tools as possible, especially in an environment where a company is paying MEGABUCKS for their Enterprise Oracle license and doesn't want to hear about another Oracle license fee.
Dai, I want you to know that despite my complaints, I LOVE JDev er. I love SQLDeveloper as well (have I mentioned that it hangs a couple of times a day and I have to kill it?).
Of course, now I'm comparing my own whining with my previous post about User Expectations. Developers are probably the hardest crowd to please as far as User Expectations go. Not only do I want the custom street rod, but I want it for free, too. :)
Thanks for reading -- "I'm not worthy..." :)
Dai responded and was wondering what was giving me problems with generating from JDev. First of all, I have to say that I'm totally flattered that he read the post and responded -- especially since I was just whining into the Black Hole of the Internet.
First, let me say that I'm totally flattered that you read my whining -- "I'm not worthy..." The JDev Modeler ROCKS.
Here's the trouble that I end up having with the generating (in version 11.1.1.0.0).
I have to choose between 'CREATE, REPLACE or ALTER.' Thus, if I've created a table and made a change to a different table, I have to generate them separately. I'd prefer that it check the connection and generate a delta. Actually, this has been my only frustration. And, if I were working on one table at a time, it wouldn't be a big deal. Yesterday, I was attempting to do just that -- create foreign keys to two existing tables, alter some other existing tables and create several new ones. Basically, I pulled in a few tables into a database diagram, made some changes and enhancements and tried to implement them. What I ended up doing was dropping the two tables that I meant to create foreign keys to and then failing to create the full set of objects. Happily, this was in Dev.
Which brings me to one of my FAVORITE features in JDev Modeler. I love that it generates the sql script. However, I would prefer to get the script always -- even when it fails to run. That way, I can look at the script and fix the script. The reason that this is my favorite feature is that I love the point and click way of rolling out changes -- but only in Development. For Production, it should be from a script.
In fact, this is one of my favorite features in SQLDeveloper as well. They have been very good to (almost) always providing a way to see a script of any change that you are making through the UI. This is a fantastic feature. As I've mentioned, i feel strongly that the script is the only way to roll the code into test and production.
At this point, I should probably confess that I've spent a few years developing with Designer. So, I was spoiled by being able to point the generator at a database connection, have it generate a delta script WITHOUT applying it, then I could go apply and test the script. Nice feature.
But again, as a former Designer user, I LOVE the JDev er. Don't tell the SQLDeveloper er team, but I like the JDev version better. Yes, it does less. However, I love that it will create a sequence and trigger for a Primary Key column with the click of a button. That's just ONE example of how the JDev Modeler is more usable. Another confession -- I stopped using SQLDeveloper er once I found out that they were going to charge for it (and since I knew that JDev already had one that rocks for free). I've been a Contractor several times and I find that it pays to be able to use as many free tools as possible, especially in an environment where a company is paying MEGABUCKS for their Enterprise Oracle license and doesn't want to hear about another Oracle license fee.
Dai, I want you to know that despite my complaints, I LOVE JDev er. I love SQLDeveloper as well (have I mentioned that it hangs a couple of times a day and I have to kill it?).
Of course, now I'm comparing my own whining with my previous post about User Expectations. Developers are probably the hardest crowd to please as far as User Expectations go. Not only do I want the custom street rod, but I want it for free, too. :)
Thanks for reading -- "I'm not worthy..." :)
2 comments:
thanks for the input. we'll take a look at that script generation issue.
dai
Hi,
If you pick ALTER it will generate CREATE statements for new objects & ALTER statements for changed ones. Maybe the option is deceptively named (will think about that for the next release).
And then check the manual reconcile option to see all the changes (you can then pick & choose if there's changes in offline & changes in the database itself.
Post a Comment