DataNucleus JIRA is now in read-only mode. Raise any new issues in GitHub against the plugin that it applies to. DataNucleus JIRA will remain for the foreseeable future but will eventually be discontinued
Issue Details (XML | Word | Printable)

Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Andy Jefferson
Reporter: Andy Jefferson
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.
DataNucleus Store RDBMS

SQLController handling of batched statements doesnt cater for waiting batched statement with already open statement needing execute

Created: 16/Jun/10 08:09 AM   Updated: 27/Jun/10 08:57 AM   Resolved: 16/Jun/10 08:38 AM
Component/s: Connection
Affects Version/s: 2.0.0.release, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.1.0.m1, 2.1.0.m2, 2.1.0.m3, 2.1.0.release
Fix Version/s: 2.1.1

 Description  « Hide
If we have the situation as follows

1. Open PreparedStatement for (InsertRequest) statement of Object A to execute
2. Start populating parts of that statement, but this causes the insert of a related object (Object B)
3. The insert of Object B could be batched
4. Open PreparedStatement for (InsertRequest) statement of Object B to execute
5. Execute statement for Object B - goes into waiting batch
6. Execute statement for Object A

Step 6 currently checks if there is a waiting batch and if it is its statement, and if so add to the batch. It doesn't check if there is a waiting batch and if it is a different statement; in that case it should just process the batch then and then execute its own statement.

Sort Order: Ascending order - Click to sort in descending order
Andy Jefferson added a comment - 16/Jun/10 08:38 AM
SVN trunk fixes this