RE: Porting Java applications from the 400 (was: SQL update/insert for a string contain " ' ")

>Buck, this is hardly ignorance.  It is instead
>one of the crucial points of designing OO business
>applications.  The datasource concept I presented in
>my previous post is the wahy to avoid that particular
>pitfall.

"Practically speaking, how likely is it that I can
 pick up my Java application, re-do the data access
 classes and be ready to go?"

The implicit question is "How many Java programmers are doing this today?"

>This technique is especially important in the
>case where the database is fundamentally different.

Yes indeed, but that presupposes that either the programmer is experienced
enough to plan ahead for this or the design specifies multiple database
access.  Would a new Java programmer really design her code this way?
Especially, would a procedural programmer moving to Java think this way?  I
bet they know that they should, but DO they?

>The best place to do it is in a single,
>encapsulated location, rather than strung
>out all over your code.

No question.  That's what us old guys are learning with ILE.  Build a
function and use it everywhere.  Need a change?  Fix the one function and
you're good to go.  The hassle is wrapping our head around just how far to
break things down.  I figure that by the time I move to Java in production,
I'll be inheriting somebody else's code (contractor?) and will then be
posting about refactoring. <grin>
  --buck