[EMAIL PROTECTED] wrote:
Justin Fletcher <[EMAIL PROTECTED]> wrote:
do_test select1-11.2.2 {
execsql2 {
SELECT * FROM t3, t4;
}
} {a 3 b 4 a 3 b 4}
Can someone explain how the test can be correct ?
This comes about because of duplicate column names.
The execsql2 procedure looks at all column names in
the result set, then returns the value associated with
each column name. So in the example above, it looks
at columns named "a", "b", "a", and "b", in that order.
But both "a" and "b" are ambiguous names. So it picks
the value that corresponds to the column that is last
in the list.
This is goofy, perhaps, but it is the way the test
system works.
That's good because it means that I'm not going crazy -
thanks :-)
As test select1-11.2.1 already produced a useful result
for this class of test and 11.2.2 provides no additional
tests, it is probably redundant as a test there - the
test it's performing is actually being obscured by the
goofy test system :-|
I'm working my way through the test suite and will need
to identify such cases. Would it be useful to report these
in order that they can be flagged as being obscured by the
test system ?
--
Justin Fletcher, Senior Software Engineer
Picsel Technologies Ltd Tel: +44 141 8855588
Titanium House, Kings Inch Rd, Glasgow, G51 4BP, UK Web: www.picsel.com
----------------------------------------------------------------------------
This email is subject to disclaimer at http://www.picsel.com/disclaimer.html
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
