Re: Caution: Bug or "feature" - row ordering within temp tables in V7.x

In article <3309EB0B.5951@ana.med.uni-muenchen.de>, Richard Spitz <spitz@ana.med.uni-muenchen.de> writes >vjaco@hcia.com wrote: >> This is one of those things that is serious enough to warrant a mass mailing >> to Informix for an immediate "feature" request. > >Don't hold your breath for that :-) Agreed. > > >> Using anybody's SQL (Sybase's, Oracle's and even Informix's), if I have an >ORDER >> BY clause in my SELECT statement, I expect to see my results ordered according >> to the criteria that I specified. Correct. > >Sure, that's what the ORDER BY clause is for. > >> Here's the problem: >> In V7.x if you are using multiple temp dbspaces (DBSPACETEMP) and you have a >> statement like the following: >> SELECT * FROM table_a INTO TEMP ORDER BY 1 temp_a> >Shouldn't it read "SELECT * FROM table_a ORDER BY 1 INTO TEM temp_a"? > >> Do not expect the rows you get back from temp_a (SELECT * from temp_a) to be Where is the order by clause ? You're select does not have one therefore the ordering is not defined. Which page in the Oracle manuals states that the default ordering in a select is the order in which rows are inserting into the table? Give me a manual reference (Oracle 7.3 for UNIX). Solution: Do not rely on undocumented features of a software release, later releases WILL work differently due to a) Bug fixes b) Performance enhancements. Software should be allowed to work internally in any way it choose to allow performance enhancements/bug fixes in later releases. -- David Williams