Humm, It _should_ work like the following.
The sequencer has a few reserved ids.
E.g.
lastId = 312
reservedUntilId=349
while (lastId == reservedUntilId)
goToDataBaseAndReserveTheNextBlock();
return ++lastId;
And you are saying it goes to the database also if there is still a block of
[
https://issues.apache.org/jira/browse/OPENJPA-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986998#action_12986998
]
Mark Struberg commented on OPENJPA-1912:
figured that I still have a few bugs
[
https://issues.apache.org/jira/browse/OPENJPA-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg updated OPENJPA-1912:
---
Attachment: OPENJPA-1912-fix-wo_cleanup-2.patch
this patch now de-externalises in the
Support fine-grained data acess control for queries
---
Key: OPENJPA-1931
URL: https://issues.apache.org/jira/browse/OPENJPA-1931
Project: OpenJPA
Issue Type: New Feature
Components:
[
https://issues.apache.org/jira/browse/OPENJPA-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Curtis reopened OPENJPA-1847:
--
Assignee: Rick Curtis (was: Michael Dick)
Found a NPE in other testing.
Use a single
[
https://issues.apache.org/jira/browse/OPENJPA-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Curtis closed OPENJPA-1847.
Resolution: Fixed
Fix Version/s: 2.2.0
Commited changes to 2.1.x and trunk.
Use a
Hi!
The spec says (3.5.2):
The PreUpdate and PostUpdate callbacks occur before and after the database
update operations to entity data respectively.
Does that mean that @PreUpdate should get called only before any real SQL
update to the database?, or always if the entity got made dirty (but
[
https://issues.apache.org/jira/browse/OPENJPA-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg updated OPENJPA-1912:
---
Attachment: OPENJPA-1912-enhancer.patch
oops, I forgot to also attach the enhancer parts
