I'm executing a SQL statement over a keyed file, yet the results come out in FIFO. Do I have to specify an "order by" clause? If so, what's the point of accessing a keyed file/table?
Here is the code that build and executes the SQL statement.
// Run an SQL SELECT statement Statement stmt = con.createStatement (); String SQLStmt = "SELECT CUSNUM,LSTNAM,INIT,STREET,CITY,STATE,ZIPCOD,CDTLMT,CHGCOD,BALDUE,CDTDUE FROM RAYLIB.QCUSTCDT01 WHERE " + SqlWhereClause; ResultSet rs = stmt.executeQuery (SQLStmt);
Originally posted by Ray Marsh: Do I have to specify an "order by" clause?
If you want results in a specific order, you have to ask for it. Full stop.
If you don't specify an "order by", the database optimiser is free to execute the query in whatever way it likes, and return the result in whatever order it happens to read the rows in. Most of the time this will be some "obvious" order, but don't ever rely on it. A change in the amount or nature of your data may prompt the optimiser to use a different execution plan and return results in a different order. Similarly, you might add a new index to the table as part of an application change and find the result order changing. An upgrade to the database may include optimiser tweaks that have the same effect. And, last but certainly not least, when read by human eyes your SQL code is not a clear expression of your intent.
All in all this is a recipe for maintenance nightmares. If you want results in a specific order, always use an "order by".
- Peter [ July 31, 2004: Message edited by: Peter den Haan ]
I'm used to an environment where the DB file accessed always produces the data in key order, unless otherwise specified. This is a change of perspective for me.
Post by:autobot
grapes are vegan food pellets. Eat this tiny ad:
a bit of art, as a gift, the permaculture playing cards