On Tue, 17 Feb 2015 09:41:56 +0000, "Tim Ward t...@telensa.com
[firebird-support]" <firebird-support@yahoogroups.com> wrote:
> 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.)

It sounds like this should be a warning, and not an error.

Mark
    • ... Eduardo guse...@gmail.com [firebird-support]
  • ... Svein Erling Tysvær svein.erling.tysv...@kreftregisteret.no [firebird-support]
    • ... 'Walter R. Ojeda Valiente' sistemas2000profesio...@gmail.com [firebird-support]
      • ... Svein Erling Tysvær svein.erling.tysv...@kreftregisteret.no [firebird-support]
        • ... Eduardo guse...@gmail.com [firebird-support]
          • ... Eduardo guse...@gmail.com [firebird-support]
            • ... 'Leyne, Sean' s...@broadviewsoftware.com [firebird-support]
              • ... Eduardo guse...@gmail.com [firebird-support]
              • ... Eduardo guse...@gmail.com [firebird-support]
              • ... Tim Ward t...@telensa.com [firebird-support]
              • ... Mark Rotteveel m...@lawinegevaar.nl [firebird-support]
              • ... Tim Ward t...@telensa.com [firebird-support]

Reply via email to