2014-10-06 19:04 GMT+02:00 Alok Menghrajani <[email protected]>:
> On Mon, Oct 6, 2014 at 4:51 AM, Lukas Eder <[email protected]> wrote:
> > I just realised that MySQL actually performs backslash escaping *in
> > addition* to double-apostrophe escaping. I guess there really is room
> for a
> > simple backslashEscaping boolean property in Settings, then... We'll
> > implement that for jOOQ 3.5.0
>
> Instead of a backslashEscaping setting, you should perhaps make it
> stringEscaping and then have database specific options, e.g.
> MySQL_BACKSLASH, PSQL_DOLLARS, etc. It will be less confusing for
> users of databases which don't need to care about this and easier for
> other set of users to tell which setting applies to them.
In fact, after I re-visited your pull request and how this feature actually
works, I believe that backslash escaping might really be the right setting
here, as it is complementary to double-apostrophe escaping, i.e. a
double-apostrophe ('') is considered the same as a backslash-escaped
apostrophe (\'). This isn't true with PostgreSQL's dollar-escaping, where
you have to choose either one...
--
You received this message because you are subscribed to the Google Groups "jOOQ
User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
