|
Comments below. Regards, Carel Teijgeler *********** REPLY SEPARATOR *********** On 2-4-03 at 16:47 Joe Pluta wrote: FROM ANOTHER POSTING: >What's REALLY sad, Carel, is that there are some AS/400 professionals who >would argue that this would be a good thing. This >opinion baffles me. I did not know a fear is an opinion. But then I do not like the thought of it. And that does not imply I disgard mySQL entirely, only for the AS/400. <sigh> and I wanted to kill the "rumour" in the bud, before ... </sigh> AND: > >2. DB2/400 - Break this on fear of death. Physical and logical files are >still (and frankly always will be) more powerful for certain >types of >applications than SQL. You want SQL on top of DB2/400, great, but leave me >the ability to design my own database and >access paths and access them the >way I want to. No matter how good an optimizer you have, it can never compete >with a good >programmer who actually knows exactly how the database will be >used. So I gather you would like DDS to support the new data types as well. I do, any way. I am not thrilled with all those newities on the box, and I do not oppose them, either. I would prefer a more critical attitude to those new features. So you can use PASE, SQL, RPG /free. It does not mean I have to it, but, unfortunately, I am forced to do so. If I have to choose between DDS or SQL to define data files I choose DDS. If others want to use SQL, it is their choice. It does not have to end up in disregarding one way to fully supoort the other. Support to the both alternatives should be given. This also applies to the new BIFs in RPG: it is a shame, that some BIFS can only be used un /free and not with fixed format syntax (sic!). I agree with Steve Richter on that to bring some enhancements to the older OS versions.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.