Subject: | |
From: | |
Reply To: | |
Date: | Thu, 7 Oct 1999 17:10:41 +0100 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Mark,
Allbase insists that you can only order by items in the select list.
<plug alert>
If you use LINKWAY ODBC Driver then this WILL allow you to not only sort by
items NOT in the select list but also to ORDER BY EXPRESSIONS!
e.g. select Description,Code,(Value * Qty) from table order by (Value *
Qty).
<end plug>
Ken Vickers
LINKWAY Development and Support
__________________________________
Computing Solutions Limited
Tel. +44 1905 794400
Fax. +44 1905 794464
mailto:[log in to unmask]
http://www.csllink.com
__________________________________
-----Original Message-----
From: Mark Wilkinson <[log in to unmask]>
To: [log in to unmask] <[log in to unmask]>
Date: 07 October 1999 15:21
Subject: ODBC Bug
>Hi All,
>
>Maybe this has already been discussed but I've found a rather obvious bug
in the
>ODBC driver (ODBCLINK/SE) supplied by HP with 5.5.
>
>I'm using MS-Access, linking in the tables and building queries. It seems
that
>the driver is doing some kind of optimisation to get some efficiency saving
by
>doing keyed reads wherever possible. If I've got a dataset with 3 fields
field1
>field2 and field3 and field1 is a (unique primary) key item, then the
extract
>seems to be done in two phases..
>
>1. select just the key item.
>2. Go back in and read the rest of the data as determined by the original
SELECT
>
>Unfortunately, if you define an ORDER BY clause, this is attempted at step
1 and
>if field3 is the sortkey then phase 1 fails.
>
>The SQL actually passed in phase 1 would look like this:-
>
>>select field1 from file1 order by field3;
>
>Big syntax error - Column field3 does not exist. You have to select the
field in
>order to sort on it.
>
>Do we have a patch for this?
>
>Cheers.
>
>Mark W.
>SPE.
>
|
|
|