OK, so SQLDeveloper is a free tool from Oracle. I really like it, but am still waiting to see some wrinkles ironed out. For example, it hangs at least twice a day and has to be killed. The PL/SQL formatting still has a LOT to be desired (in fact, the tool seems to be just treat PL/SQL as if it were straight SQL). It still has problems with the File Navigator, importing and exporting Excel spreadsheets, etc. The great thing was that until a year ago, SQLDeveloper was making fairly steady progress. So, if you saw a bug, there was some hope that it would get fixed -- at least partially -- in the next release.
SQLDeveloper is built from JDeveloper -- also free. JDeveloper is fine for Java, but not so hot for PL/SQL (hence, SQLDeveloper, which does better with SQL but still struggles with PL/SQL).
JDeveloper has a data modeler. It's actually quite nice, but has a few quirks -- like the fact that generating is a pain in the butt.
SQLDeveloper Data Modeler is not free, is not built from JDeveloper's data modeler, and is not part of SQLDeveloper. In fact, it appears to be totally unrelated. In testing the pre-release version, it looked like it was some dead Oracle product that got revived and assigned.
And the really crappy thing? Well, it appears that the SQLDeveloper team has been so busy building the SQLDeveloper Data Modeler (instead of just integrating the one that's already in JDeveloper), that each new version of SQLDeveloper has almost nothing in it.
And why are they doing this? Apparently so they can charge for SQLDeveloper Data Modeler. Did I mention that JDeveloper has a free Data Modeler?
??????????
Oracle, you confuse me.
SQLDeveloper is built from JDeveloper -- also free. JDeveloper is fine for Java, but not so hot for PL/SQL (hence, SQLDeveloper, which does better with SQL but still struggles with PL/SQL).
JDeveloper has a data modeler. It's actually quite nice, but has a few quirks -- like the fact that generating is a pain in the butt.
SQLDeveloper Data Modeler is not free, is not built from JDeveloper's data modeler, and is not part of SQLDeveloper. In fact, it appears to be totally unrelated. In testing the pre-release version, it looked like it was some dead Oracle product that got revived and assigned.
And the really crappy thing? Well, it appears that the SQLDeveloper team has been so busy building the SQLDeveloper Data Modeler (instead of just integrating the one that's already in JDeveloper), that each new version of SQLDeveloper has almost nothing in it.
And why are they doing this? Apparently so they can charge for SQLDeveloper Data Modeler. Did I mention that JDeveloper has a free Data Modeler?
??????????
Oracle, you confuse me.
2 comments:
Hey, one of my teams builds the JDev modeler & DB tools (those that we don't share with SQLDev).
You wouldn't like to share why the generating is a pain in the butt would you?
Not cos i'm gonna argue with you - just take it on board to make it better. General principles, specific cases, versions of JDev would help.
Cheers
dai clegg
dai,
I did respond, but in a separate post. Just in case this happens again, if you see the words "JDev er" in my post, it's really "JDev Modeler" -- somehow Blogger keeps stripping out the word "Model" from my post.
--s
Post a Comment