Why?? Why does that have to be a failure?? Why can't Firebird just ignore it??
Is there any switch to turn off this behaviour?? (I've got some immensely complicated query generation code which, it now appears, can occasionally include a common table expression in the query that isn't actually used anywhere. I've now got to fix that code to be extremely careful about *ex*cluding unneeded CTEs - it's currently aimed at being extremely careful to *in*clude CTEs that *are* needed.) -- Tim Ward ------------------------------------ ------------------------------------ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Visit http://www.firebirdsql.org and click the Documentation item on the main (top) menu. Try FAQ and other links from the left-side menu there. Also search the knowledgebases at http://www.ibphoenix.com/resources/documents/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ------------------------------------ Yahoo Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/firebird-support/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/firebird-support/join (Yahoo! ID required) <*> To change settings via email: [email protected] [email protected] <*> To unsubscribe from this group, send an email to: [email protected] <*> Your use of Yahoo Groups is subject to: https://info.yahoo.com/legal/us/yahoo/utos/terms/
