[jira] [Resolved] (METAMODEL-142) Create JDBC table within an UpdateScript and with connection pool returns a null table

["Kasper Sørensen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/METAMODEL-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kasper Sørensen resolved METAMODEL-142.
---------------------------------------
    Resolution: Fixed
      Assignee: Kasper Sørensen

Fixed, thanks for the review and accept.

> Create JDBC table within an UpdateScript and with connection pool returns a null table
> --------------------------------------------------------------------------------------
>
>                 Key: METAMODEL-142
>                 URL: https://issues.apache.org/jira/browse/METAMODEL-142
>             Project: Apache MetaModel
>          Issue Type: Bug
>            Reporter: Kasper Sørensen
>            Assignee: Kasper Sørensen
>
> If you execute an update on a JdbcDataContext based on a connection pool in which BOTH creates a new table and starts inserting records to it, then it may fail.
> To be specific, a table returned by the TableCreationBuilder will return null:
> {code}
> final Table table = tableBuilder.execute();
> {code}
> Our JdbcMetadataLoader is loading tables from the schema like this:
> {code}
> @Override
> public void loadTables(JdbcSchema schema) {
>     final Connection connection = _dataContext.getConnection();
>     ...
> {code}
> But since a new connection will be used here, and the other connection is still in an active transaction, then the isolation criterium of the transaction will cause this to NOT include the newly created table in the metadata



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)