OK, I will do my best to match *exactly* what is expected. I will look
at some of the existing stuff to use as a pattern. However, I will have
to leave it to you or whomever does the ODBC tests to make sure it works
for ODBC.
David
Army wrote:
David W. Van Couvering wrote:
OK, thanks. I hadn't considered the RS metadata.
Just a note that the result set metadata should match the defined
results _exactly_. Returning an int where a short is expected, or a
char where a varchar is expected, or a nullable column where a "not
null" column is expected, etc. etc. can cause existing applications a
lot of problems--see DERBY-107. Our JDBC tests might not catch it, but
my past experience is that ODBC applications (esp. Microsoft ones like
Access) will throw a fit if something is even slightly off...
Army
begin:vcard
fn:David W Van Couvering
n:Van Couvering;David W
org:Sun Microsystems, Inc.;Database Technology Group
email;internet:[EMAIL PROTECTED]
title:Senior Staff Software Engineer
tel;work:510-550-6819
tel;cell:510-684-7281
x-mozilla-html:TRUE
version:2.1
end:vcard
