On 4/28/14 8:58 AM, Alan Campin wrote:
The funny thing about this to me is how people are always saying there are
no costs to using file I/O and bringing the entire database into the
program. In other words, no database independence.
Just watching this one thread and you have the real costs. Billions spent
dealing with problems like this where we should just be able to increase
the field size and recompile the few programs that use the PO fields which
is what anyone else using SQL on other systems is doing.
But recompiling things that aren't "core code" of a published product is
usually a trivial exercise.
In my first example, I was talking about one customer requiring a longer
version of something that was part of the core product. And in the
second, it wasn't a database field at all, but an internal data structure.