Did I mention that I really really dislike Derby? No.. Well now you know.
What on earth is wrong with the Derby developers, is it really really that hard to print sensible error messages? It is? Then maybe they need to hire a 4 year old as they would be able to suggest some more intelligent error messages. Don’t believe me? Check out the following error message:
ij> select * from blahs;
ERROR 42X05: DB2 SQL error: SQLCODE: -1, SQLSTATE: 42X05, SQLERRMC: BLAHS42X05
Is it really so hard to just say that ‘blahs’ doesn’t exist like any other DB would? If thats not enough there is no way of looking at the table structure (At least not that I could find) or my personal faveroite: no way todump an entire DB to a file for archiving or convertion to another DB. Every other DB I have worked with has let me do this but derby… Arrghh…
In case you are wondering I wasted almost all day today with Scott trying to export data from Derby to Postgresql. Finally Scott ended up creating a Java program to read the data from derby and create SQL statements which can them be imported in any DB.
If any Derby developer is reading this: get your act together, the goal is not to make an impossible to use DB (Though if it was then you have suceeded) it is to make a simple and user friendly system… Go read a few books on usability
– Suramya
Any reason you still using Derby then?
Unless the evil boss is forcing it on you
Hehe!
Comment by Vinit — October 20, 2005 @ 12:35 AM
Nope no reason… Thats my we are migrating.
Finally convinced the evil boss to switch to Postgresql (Wanted to switch to MySQL but anything is better than Derby)
– Suramya
Comment by Suramya — October 20, 2005 @ 12:41 AM
Whoaaaaaaaaaaaaa
Sarcastic and touchy!
Comment by St — October 24, 2005 @ 5:10 PM