I'm actually still unsure of what to do with these statements...
SQL-92 only allows double dash (--) comments. /* */ have been
introduced in SQL-99
The other problem is that most of the time, these lines are interpreted
by mysql server directly, but can contain armful statements such as set
character_set... (which are forbidden with connector/j)
Anyway, I will file a bug so we can discuss this.
Cheers,
Gilles.
Emmanuel Cecchet wrote:
Hi Gilles,
Should we add a lookup for /* ... */ in all regular expressions so that
we don't parse comments and detect empty queries?
Is /* ... */ a SQL standard or another MySQL specific extention?
Also in your comment, does that mean that Sequoia remaps
Statement.execute("/* ... */") to Statement.executeQuery("/* ... */")?
We should probably file a JIRA entry for this bug with empty queries.
Thanks for the comments,
Emmanuel
This one looks like the SET command is executed as a SELECT instead of
an update. Therefore the controller cannot build a ResultSet since there
is no result for it. I don't know if this is a Myosotis problem or a
Sequoia parser issue.
Actually, this is more a sequoia parser issue, where empty requests
(in your case /* .... */) are not handled properly.
These empty requests should be sent to backends with a
statement.execute() (rather than with current statementExecuteQuery())
(need to confirm if that would work!)
Cheers,
Gilles.
--
Emmanuel Cecchet
FTO @ Frog Thinker
Open Source Development & Consulting
--
Web: http://www.frogthinker.org
email: [EMAIL PROTECTED]
Skype: emmanuel_cecchet
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
|
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
