Yes, not only would the alternative syntax NOT fix the problem, but it could
seriously impact your performance. I recently analyzed a JDBC application
for performance problems (using JProbe) and found that 2/3 of my time was
being spent by the driver looking up my column number with the name.
Always refer to columns by number, and read them all in one time -- first to
last -- into a data structure from which you can randomly access what you
need how you need it.
-----Original Message-----
From: Ralph Einfeldt [mailto:[EMAIL PROTECTED]]
Sent: Sunday, May 27, 2001 11:31 PM
To: '[EMAIL PROTECTED]'
Subject: AW: JDBC/ODBC: Technological choice
It's not bizarre, just what JDBC API doc tells:
"For maximum portability, result set columns within each row
should be read in left-to-right order, and each column should
be read only once."
> -----Urspr�ngliche Nachricht-----
> Von: Alexandre Bouchard [mailto:[EMAIL PROTECTED]]
> Gesendet: Donnerstag, 24. Mai 2001 21:49
> An: [EMAIL PROTECTED]
> Betreff: Re: JDBC/ODBC: Technological choice
<snip/>
> That's really bizar... And that sucks. Where does this
> limitation come from?
> The driver? Access? Would this alternative syntax:
> String x = getString(String columnName)
> do the same thing? Where could i find a list of these
> "bugs"/limitations.
> And what about a driver of type IV, would there be the same
> limitations?
<snip/>
