Back to the month index |
Back to the list index
|
David J. Hughes (bambi@Hughes.com.au)
Tue, 7 Jan 1997 21:22:02 +1000 (EST)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- Next message: David J. Hughes: "Re: [mSQL] 2.0 - can it cache results?"
- Previous message: Fernando Lozano: "[mSQL] mSQL and OS/2 apps"
- Next in thread: Thomas Baetzler: "Re: [mSQL] ORDER BY + _rowid == bug?"
- Reply: Thomas Baetzler: "Re: [mSQL] ORDER BY + _rowid == bug?"
Date: Tue, 7 Jan 1997 21:22:02 +1000 (EST) From: "David J. Hughes" <bambi@Hughes.com.au> Subject: Re: [mSQL] ORDER BY + _rowid == bug? Message-Id: <Pine.SUN.3.91.970107212045.2365I-100000@webster.AusWeb.com.au>
On Sat, 4 Jan 1997, Alex Tang wrote:
> The _rowid variable is an "internal" variable (as per the documentation),
> and is retreived off of the table data structure. The problem is that
> when a temporary table is created, the _rowid returned in the select query
> is the _rowid of the >temporary table<, not of the original table, so the
> _rowid may not correspond with the original table.
That's true. I guess that the rowid should be stored as a "real" column
in the result table during processing. This would get over the problem
(although it'd add to the logic a bit).
I'll have a think.
Bambi
...
--------------------------------------------------------------------------
To remove yourself from the Mini SQL mailing list send a message containing
"unsubscribe" to "unsubscribe" to msql-list-request@bunyip.com. Send a message containing
"info msql-list" to majordomo@bunyip.com for info on monthly archives of
the list. For more help, mail owner-msql-list@bunyip.com NOT the msql-list!
- Next message: David J. Hughes: "Re: [mSQL] 2.0 - can it cache results?"
- Previous message: Fernando Lozano: "[mSQL] mSQL and OS/2 apps"
- Next in thread: Thomas Baetzler: "Re: [mSQL] ORDER BY + _rowid == bug?"
- Reply: Thomas Baetzler: "Re: [mSQL] ORDER BY + _rowid == bug?"