[Date Prev][Date Next]
RE: (ITS#3541) ResultSet getString(int i)
Your answer certainly agrees with my observations.
However, I was under the impression that the SQL standard did specify
the order of return when the programmer specified explicit columns in
the select statement (did not use something like the * notation).
As least this is the way I have seen every SQL vendor I ever dealt with
before (Oracle, Informix, Sybase). Anc certainly the order of results
did not change between rows of the result set :-(
IMHO, this is probably not an openLDAP slapd issue, rather it is a
surprising feature of the JDBC-LDAP Bridge Driver (JDBC-LDAP) by
I've stopped 3,102 spam messages. You can too!
One month FREE spam protection at http://www.cloudmark.com/spamnetsig/}
From: Pierangelo Masarati [mailto:email@example.com]
Sent: Saturday, February 19, 2005 4:31 AM
Subject: Re: (ITS#3541) ResultSet getString(int i)
>Full_Name: Charles Robinson
>Version: doc says 0.1 zip suggests 2.0
>OS: Wiin 2000
>Submission from: (NULL) (188.8.131.52)
>When analyzing the ResultSet derived from a Select as follows (notice
>explicit names in the select)
>ResultSet rs = stmt.executeQuery("SELECT
>cn,displayName,givenName,department,mail FROM ou=Users where
>I found that if I did a rs.getString(1) I got a random column.
>I converted to rs.getString("cn") and got the column named.
>It looked as if the result set was ordered by whatever order LDAP
>back, not what the programmer specified in the select.
It is unclear what client software is being used; it seems o be
unrelated to OpenLDAP software. In any case, OpenLDAP's slapd returns
the attributes in an implementation dependent order that may be totally
unrelated to the order they are requested; there is no indication in the
specs as per what order attributes must be returned.
SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: