https://bugs.freedesktop.org/show_bug.cgi?id=53867
--- Comment #12 from Alex Thurgood <[email protected]> 2012-08-23 18:12:01 UTC --- (In reply to comment #8) Hi Tyler, > When you connected to MySQL, under 'Connect to an existing database' did you > choose MySQL? On the next screen, 'Set up MySQL Connection', is where I > specified to use the JDBC. I only stress this because I'm aware of JDBC being > an option at the beginning, and (while it probably does) I'm not sure if it > works the same. Yes, I have had a JDBC mysql connection set up to one of my work database servers for the last 6 or 7 years, as a backup for the native mysql connector in case that gets broken by LO development (which it has, unfortunately, on more than one occasion). > > I leave the future of this report up to you as you have more experience than > I. > On my end, the SQL parser will not let statements with DATE_ADD or DATE_SUB > through, but turning the parser off allows me to run the same statement with > no > error. That sounds like a bug to me, but as I develop all of my queries in > MySQL first, I'll probably never turn the Parser back on anyway (I won't have > to add grave accents). > > As this is a problem with the SQL Parser (on my end at least), my original bug > description may not be valid anymore. Since I can just turn the parser off, I > can get back to business. The parser used by LO internally is, ermmm, how can I say, "suboptimal", and has been for a long time. It tries to be all things to all database engines, which unfortunately is a Herculean task, and something in the end that it doesn't do very well when it comes to what many would consider to be basic SQL functions (for that user's respective database). Add to that the fact that sometimes the db engines or their drivers do not always tell LO the truth about their own capabilities (over/understated), and you have a recipe for disaster, or at least, many "gotchas", which only can be avoided by direct SQL processing. So, I'm going to close this bug as invalid, since it appears to me that this is a limitation of the parser and not a buggy piece of code. If you want to open up a request for enhancement bug relating to support in the parser for "advanced mysql functions", please go ahead, it'll be another one added to the pile ;-) Alex -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
