> Can anybody tell me, what the problem really is??? Is there a need to
> mask curly brackets in any way? How can I avoid the problem (or at least
> bypass it)?

This is a bug in our parser in Jaybird driver that is supposed to parse
escaped sequences. Interesting enough, the parser was not changed for very
long time (I'd say two years or even more)...

No workaround except using parameters is available. We will fix it as soon
as possible and release a point version.

Roman