Hi Everyone I'm migrating from SQLAnywhere 7 to version 12 and came across this strange behaviour:
1) Using ODBC and trying to do a SELECT in a view that returns no rows. 2) It shows a GENERAL SQL ERROR. 3) When I order the view, this problem is solved, eg, SELECT * FROM view ORDER BY <field>.
The question is: is there any flag that could turn this behaviour back to the same as version 7? My concern is that I use views a lot and could spot this error but cannot afford to review every view to solve this issue.
Is the statement returning a true error, or a warning?
A change in releases subsequent to version 7 was to issue a warning (+122) if a query contained SELECT TOP but the query did not contain an ORDER BY clause.
What is the precise error you are getting?
answered 10 Nov '11, 13:56