On Fri, 2008-07-18 at 10:16 -0500, DeLong, Eric wrote:
I really must call you on the following:
"Among other challenges, SQL does not work worth a damn on program-described files in the S/36 e.e."
Now, tell me, what DBMS anywhere could work on "myData.txt"....
None at all.
My intent was to make fun of myself for being discombobulated at losing
tools which I had never missed during the decades I worked without them.
I should have made the joke explicit.
In actuality, you COULD work SQL over a file in QS36F, with a set of UDFs to convert packed numeric strings into values. Even files in QS36F are database tables on OS400, albeit they are single column character tables. Yes, it could still be a lot of work to do it this way, but I'm sure we've all used CPYF map that data into an externally described table.
I think that is what I ended up doing. I deemed this a case where an
external description would pay for itself with the first use.
There's even IDDU (yuk) that allows you to map QS36F files to an external definition, for use in queries.... You have more facilities to support the use of flat data than any other platform I can think of....
Yes. It is shocking or amusing (depending on which way your mind is
bent) to consider how deeply ingrained are the habits of using one set
of tools to the exclusion of others. No logic here, just habits.