This issue will be tracked as #2560: https://github.com/jOOQ/jOOQ/issues/2560
2013/6/26 Lukas Eder <[email protected]> > > > > 2013/6/26 Alexander Ryzhov <[email protected]> > >> I agree, it's totally MySQL's fault. To your suggestion, we already have >> databases in production where schema names are in uppercase and table names >> are in lowercase. From now on, I'll be designing MySQL databases with >> schema and table names in lower case. However, a flag for case sensitivity >> in JOOQ would be really helpful because in some cases you can't just wipe >> out your schema or even change those server settings without breaking >> existing code. > > > Yes, of course, productive systems cannot be changed easily, and I think > that MySQL made some progress since the early days where InnoDB wasn't > available yet, but only MyISAM. > > Adding a case-insensitivity flag in jOOQ *might* solve some problems, but > it is extremely hard to get things right that are not entirely predictable, > which is why I tend to suggest to take control of case-sensitivity, > explicitly, most specifically with MySQL. For instance, if this flag was > introduced in jOOQ, what should be the casing in generated classes? Upper, > lower, as_is? Will rendered SQL remain case-insensitive? > > I hope I will have some time soon, to investigate this, but as I said, > these things are mine-fields, and I'm not sure if I can get it right any > time soon. > -- 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/groups/opt_out.
