|
It's frustrating but - believe it or not - IBM said that to have the java getColumnLabel return the full label required "a lot of coding". Furthermore it seems that this feature degrades the performances and that's why you must request it with the "extended metadata". Maybe they did not want to have such "lot of coding" with sqlda. ----- Original Message ----- From: "Larry Ducie" <larry_ducie@xxxxxxxxxxx> To: <rpg400-l@xxxxxxxxxxxx> Sent: Tuesday, March 15, 2005 12:18 PM Subject: Re: Using QSQPRCED and long field names > Hi Beppe, > > <snip> > The "Table 81. Field Descriptions for an Extended SQLVAR" in the > DB2 UDB for iSeries SQL Reference V5R2 says: > > - For a label, the database manager sets this to the first 20 bytes of the > label. > - For a column name, the database manager sets this to the column name. > > while the java method "getColumnLabel" returns the full label (with the > latest ptf's) > </snip> > > Yeah, I'd seen that - I was hoping I'd missed something. I just can't > understand why the DB manager only provides the first 20 bytes of a SQL > label when the SQLDA provides a 30 byte field to describe into. It just > doesn't make sense - especially when the java drivers can retrieve the full > label. > > Totally frustrating!!! > > Oh, love the SQL2XML utility you wrote - you could say it was inspirational. > :-) > > Cheers > > Larry Ducie > > > -- > This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list > To post a message email: RPG400-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/rpg400-l > or email: RPG400-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/rpg400-l. >
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.