|
Hi Charles, I think Vern is probably right -- they probably started allowing this when they started getting serious about SQL. If that's the case, it seems odd that they would mess with the AS400 object naming, since they're translating it anyway via QADBXREF. It's like they're using the quotes instead of a flag to say that the long name is case-sensitive, but they could've kept that convention within SQL, or made it an SQL session option. The way they did it affects all objects on the AS400, e.g. CRTJOBD JOBD(QGPL/"^^^") is also valid, not just SQL-accessible objects. Oh well, there's probably some good reason that escapes me at the moment on this hot sunny Friday the 14th; aw gee, missed Friday the 13th by a day. What was it Pogo used to say about that? Thanks for the feedback! Peter Dow Dow Software Services, Inc. www.dowsoftware.com 909 793-9050 voice 909 793-4480 fax > -----Original Message----- > [mailto:midrange-l-bounces+maillist=dowsoftware.com@xxxxxxxxxxxx]On Behalf Of Wilt, Charles > The reason that it's in quotes is to keep the mixed case in the name. > > Without the quotes, the iSeries would uppercase all the names. > > > You can actually do the same thing yourself in STRSQL. > > Create table "MyTable" .... > > Select MYFLD1 as "My Field".... -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.12.0/134 - Release Date: 10/14/2005
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.