[ https://forge.continuent.org/jira/browse/SEQUOIA-1118?page=comments#action_14783 ]
Markus Wolf commented on SEQUOIA-1118: -------------------------------------- Optionally a savepoint could be created directly before the schema refresh queries for databases supporting this. With postgres a transaction is resumed when rolled back to the last savepoint. > Schema refresh in a transaction fails if sequoiaSAbase does not exist > --------------------------------------------------------------------- > > Key: SEQUOIA-1118 > URL: https://forge.continuent.org/jira/browse/SEQUOIA-1118 > Project: Sequoia > Type: Bug > Components: Core > Versions: sequoia 2.10.10 > Reporter: Emmanuel Cecchet > Priority: Critical > Fix For: Sequoia 4.0 > > > As reported by Markus Wolf on the mailing list, if you have a transaction > like: > BEGIN > CREATE TABLE xxx > ---> schema refresh here will cause a failed "select * from sequoiaSABase > where objectType=?" in DatabaseSQLMetaData if the table does not exist. > Transaction must be rollback at this point if you use Postgres or any > database that aborts a transaction as soon as an error is detected in a > transaction. > This code has been removed in Sequoia 4 but no fix is currently scheduled for > 2.10. > Creating an empty sequoiasabase table should solve the problem for 2.10 > versions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://forge.continuent.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
