On 26-10-2013 14:41, Dmitry Yemanov wrote: > 26.10.2013 16:07, Mark Rotteveel wrote: > >> If I explicitly specify the connection dialect (isc_dpb_sql_dialect), >> then it does work. I was under the assumption that if no explicit >> dialect is specified, that Firebird uses dialect 3. Is that assumption >> wrong? > > It is wrong. No dialect passed means that the client is too old so that > it has no idea about SQL dialects. The engine implies the legacy dialect > 1 in this case.
Jaybird by default does not pass the dialect and has no problems with executing queries with quoted identifiers, only when I explicitly set it to dialect 1 does it result in errors as a result of the quoted identifiers. Although that might be caused by the fact that you need to explicitly pass the dialect every time you call prepare and Jaybird there defaults to dialect 3. Mark -- Mark Rotteveel ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
