Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsWhite Papers
Discussion GroupsFirst AidDatabasesJavaBeansGUIJava 3DVirtual MachineCORBASecurityToolsGeneral
Java DirectoryOpen Source ProjectsSample Book ChaptersUser GroupsWeb Resources
Related Topics
Databases.NETMore Topics ...

Java Forum / Databases / June 2004

Tip: Looking for answers? Try searching our database.

SQL and the LGP-30

Thread view: 
Roedy Green - 18 Jun 2004 07:37 GMT
You can see a picture of my first personal computer, an LGP-30 at
http://mindprod.com/jgloss/mindprod.com/equipment.html

It had no transistors, just tubes, a rotating drum, and a few diodes.

You programmed the thing with absolute addresses, a hex track and
sector number on the drum.

Programming with JDBC took be back to those thrilling days of
yesteryear. Every parameter is numbered, one based.

I can't believe the incompetence of this intefarce.

At the very least it should have named parameters in the
prepareStatement.

It is a nightmare trying to write code where the PreparedStatements
are nowhere near the code that has to used counted fieldnames in them.
You CAN'T proofread the damn things.

Further the debugging tools to figure out what is going on are
non-existent.  You have to pepper your code with debug output to
narrow down where the problem is.

You can't even cut and paste into MySQL to test the SQL.

You'd think after 30 years or so they have got this stuff polished.

Signature

Canadian Mind Products, Roedy Green.
Coaching, problem solving, economical contract programming.
See http://mindprod.com/jgloss/jgloss.html for The Java Glossary.

Roedy Green - 18 Jun 2004 08:44 GMT
>You'd think after 30 years or so they have got this stuff polished.

What needs to happen is a tighter integration of Java and SQL.

Then you could do compile time checking to make sure column names are
correct and the types of local variables could be generated from the
database. The syntax of prepared statements could be analysed and
verified at compile time.

It might be another layer similar to the way JSP is implemented.

SQL allows fully dynamic work that could not be type checked, but the
bread and butter stuff could be.  It is much like Java itself where
most of the time you can use typechecking, but for fully dynamic work
you can subvert the type system.

There is no reason not to lock the local variable names to being the
same as the column names.

Signature

Canadian Mind Products, Roedy Green.
Coaching, problem solving, economical contract programming.
See http://mindprod.com/jgloss/jgloss.html for The Java Glossary.



Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.