Volker,
jdbc:sequoia://localhost/myDB (user) > SET NAMES utf8
Affected rows: 0
Query executed in 1 s 216 ms .
jdbc:sequoia://localhost/myDB (user) > SET NAMES utf8
An error occured while executing SQL query
(org.continuent.sequoia.common.exceptions.driver.DriverSQLException:
Message of cause: Unable to clone the parsing of an unknown request)
...
Conclusions:
* Sequoia is not capable to know the change of the charset since this
is higly DB-spezific.
* So if the charset is changed during a DB-session sequoia will fail.
Anyone an idea to workaround this problem?
I don't think that the issue is related to the charset at all, it is
mostly due to the parsing cache. I don't know why an unknown request
would be inserted there but that's mostly the root cause.
Could you disable the parsing cache from your configuration file and
give it another try? If it works without the parsing cache, please file
a bug so that we can fix the cache.
Thanks for your feedback,
Emmanuel
--
Emmanuel Cecchet
Chief Scientific Officer, Continuent
Blog: http://emanux.blogspot.com/
Open source: http://www.continuent.org
Corporate: http://www.continuent.com
Skype: emmanuel_cecchet
Cell: +33 687 342 685
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
