|
CRAP SHOOT CRAP SHOOT! <grin> Actually, I just had a related problem. The exact same data in the exact same file in (as far as I can tell) the exact same order on two different machines. The same SQL statement without an ORDER BY returned the data differently on the two machines. The SELECT criteria should have caused the SQL engine to use the same index (it was a keyed physical file and the selection fields were the first three of six fields in the key), but until I added an ORDER BY over all six fields, I was not getting the same sequence on the two machines. Joe > From: Holden Tommy > > Question is is there any trade off by specifically declaring the ORDER > BY in conjunction with the GROUP BY. I'd prefer to know beyond the > shadow of a doubt that my data will be in the order I desire. Should > someone (for whatever reason) delete/modify that logical view what would > happen then? Would you still receive the same data order as you were > expecting or would it be a "crap shoot"???
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.