Hi Ian,
Using last_insert_id() is a bad idea, you should use the JDBC 3 call
Statement.execute(sql, RETURN_GENERATED_KEYS).
If you cannot modify your code and must use last_insert_id(), you have
to call it on the same connection than the one that was used for the
update (which does not work with a connection pool unless this is done
within a transaction). Sequoia has a workaround for that called
persistent connections that you can pass as an option to the Sequoia
driver. More info about that feature in the doc at
http://sequoia.continuent.org/doc/infocenter/topic/org.continuent.sequoia.doc/html/Sequoia_URL_options.html
Hope this helps,
Emmanuel
I thought I posted about this earlier, but I don't see the message in
the archives. I apologize if this is a duplicate.
Anyone have a solution for using MySQL sequences with Sequoia?
We're using fake MySQL sequences using the parameterized
last_insert_id() technique (described at
http://www.mysqlperformanceblog.com/2008/04/02/stored-function-to-generate-sequences/
among other places).
Using the stored function, we're seeing duplicate sequence entries.
Executing the update/select statements outside of a function, we're
seeing duplicate sequence entries.
Using a stored procedure, we're not seeing duplicate sequence entries,
but performance is poor.
What's a guy to do?
Thanks,
Ian.
------------------------------------------------------------------------
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
--
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
