|
Okay, lets look at dBase, Clipper, Foxpro, BTrieve, Access, am I leaving any out? I seem to recall that if I changed the layout of a database in any of those languages I would not have to recompile unless I removed a field that was being used in one of those programs. The distinction is: those programming languages (and the underlying database architecture) get the file layout from the file itself, not from an internal declaration. Which is how I was hoping RPG would do it. RPG already has access to the layout of the file at run time, does it not? Yes, I understand it would take longer at program initialization for RPG to retrieve the layout from the data base file. And I understand that RPG is not doing that now, because it didn't in the past. But, what is stopping it now? Regards, Jim Langston pytel@us.ibm.com wrote: > I see a kind of confusion here: > > > Just about every other data base in the world does this but not the > AS/400. > > AS/400 database is certainly doing this for you. Native I/O provides static > database independence - you only have to recompile the program if you change >the > file. It also provides tools to improve this independence - logical files >(more > about it later). > If you want dynamic database independence - AS/400 provides it via SQL > interface. > You should compare apples to apples - native Database Access should be >compared > to native I/O for UNIX or NT - which is unformatted stream of bytes. > If you compare AS/400 to Oracle, for example, then to be fair you should use > OS/400 SQL for comparison. <SNIP> +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.