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

> -----Original Message-----
> From: Buck Calabro
>
> 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?

They would if they were trained by me <smile>.  In my classes, I stress the
fact that Java is NOT a procedural language, that it's an OO language, and
that you need to think OO to take advantage of it.  Writing procedural code
in Java is like teaching a pig to sing: it doesn't accomplish much, and it
annoys the pig.

The thing I've found during my years of teaching, though, is that once a
programmer is introduced to these concepts, they're very receptive.  Why?
Because they make sense.  It's not that programmers can't understand OO
concepts, just that they've never seen them.  Once they see them, they tend
to eat them up.  There is a certain percentage of folks who will never make
the leap, but that number is surprisingly small.  I've taught classes full
of mainframe COBOL folks, and, after some initial culture shock, they loved
it.  Why?  For two reasons:

1. You only write things once
2. You only debug things once

For COBOL folks especially, not having to type out all that stuff again,
simply being able to call a method, was definitely a GOOD THING.

Joe