[jira] Created: (OPENJPA-1677) "InvalidStateException: Detected reentrant flush..." while building an error message for an earlier exception

"InvalidStateException: Detected reentrant flush..." while building an error message for an earlier exception - Key: OPENJPA-1677 URL: https://issues.apach

[jira] Commented: (OPENJPA-1677) "InvalidStateException: Detected reentrant flush..." while building an error message for an earlier exception

[ https://issues.apache.org/jira/browse/OPENJPA-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874640#action_12874640 ] Vermeulen commented on OPENJPA-1677: Even worse, when I first merge a new entity that

[jira] Updated: (OPENJPA-1677) "InvalidStateException: Detected reentrant flush..." while building an error message for an earlier exception

[ https://issues.apache.org/jira/browse/OPENJPA-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-1677: --- Attachment: openjpa-1677_sscce.zip This sscce contains two entities and a JUnit 4 test which shows

[jira] Created: (OPENJPA-1919) Entity contains pseudo-attached ElementCollection map after detach

Entity contains pseudo-attached ElementCollection map after detach -- Key: OPENJPA-1919 URL: https://issues.apache.org/jira/browse/OPENJPA-1919 Project: OpenJPA Issue Type: Bug

[jira] Commented: (OPENJPA-1919) Entity contains pseudo-attached ElementCollection map after detach

[ https://issues.apache.org/jira/browse/OPENJPA-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978795#action_12978795 ] Vermeulen commented on OPENJPA-1919: I accidentally had two different values for the

[jira] Updated: (OPENJPA-1919) Entity contains pseudo-attached ElementCollection map after detach (with DetachedStateField=false)

[ https://issues.apache.org/jira/browse/OPENJPA-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-1919: --- Summary: Entity contains pseudo-attached ElementCollection map after detach (with DetachedStateFiel

[jira] Created: (OPENJPA-1920) N+1 select with entities that contain Maps (even with FetchType.EAGER)

N+1 select with entities that contain Maps (even with FetchType.EAGER) -- Key: OPENJPA-1920 URL: https://issues.apache.org/jira/browse/OPENJPA-1920 Project: OpenJPA Issue Ty

[jira] Commented: (OPENJPA-673) Entity using Generated Value for primary key and a Version field and no DetachedStae fails to merge

[ https://issues.apache.org/jira/browse/OPENJPA-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986406#action_12986406 ] Vermeulen commented on OPENJPA-673: --- I had the same kind of exception as himakiran. It

[jira] Created: (OPENJPA-1947) hsqldb and GenerationType.IDENTITY generates incorrect sql when the table has only one column

hsqldb and GenerationType.IDENTITY generates incorrect sql when the table has only one column - Key: OPENJPA-1947 URL: https://issues.apache.org/jira/browse/OPENJPA-1947

[jira] Commented: (OPENJPA-1066) Generated ID starting with 0 can cause unexpected results

[ https://issues.apache.org/jira/browse/OPENJPA-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997420#comment-12997420 ] Vermeulen commented on OPENJPA-1066: I was making a test case for another problem (w

[jira] Commented: (OPENJPA-1066) Generated ID starting with 0 can cause unexpected results

[ https://issues.apache.org/jira/browse/OPENJPA-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997426#comment-12997426 ] Vermeulen commented on OPENJPA-1066: Don't know if this helps, but I found a similar

[jira] Updated: (OPENJPA-1066) Generated ID starting with 0 can cause unexpected results

[ https://issues.apache.org/jira/browse/OPENJPA-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-1066: --- Comment: was deleted (was: Don't know if this helps, but I found a similar bug on EclipseLink (htt

[jira] Issue Comment Edited: (OPENJPA-1066) Generated ID starting with 0 can cause unexpected results

[ https://issues.apache.org/jira/browse/OPENJPA-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997420#comment-12997420 ] Vermeulen edited comment on OPENJPA-1066 at 2/21/11 2:47 PM: -

[jira] Updated: (OPENJPA-1947) GenerationType.IDENTITY generates incorrect sql when the table has only one column

[ https://issues.apache.org/jira/browse/OPENJPA-1947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-1947: --- Description: I use hsqldb for simple tests and let OpenJPA generate the tables with the line in pe

[jira] Created: (OPENJPA-1949) inserting new entities to the front of an existing List fails when using GenerationType.IDENTITY

inserting new entities to the front of an existing List fails when using GenerationType.IDENTITY Key: OPENJPA-1949 URL: https://issues.apache.org/jira/browse/OPENJPA-

[jira] Updated: (OPENJPA-1949) inserting new entities to the front of an existing List fails when using GenerationType.IDENTITY

[ https://issues.apache.org/jira/browse/OPENJPA-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-1949: --- Attachment: OPENJPA-1949-TestCase.zip My own standalone JUnit 3 TestCase for this problem. > inser

[jira] Created: (OPENJPA-1950) exception when converting datetime2 result from String to java.util.Date (ms sql server)

exception when converting datetime2 result from String to java.util.Date (ms sql server) - Key: OPENJPA-1950 URL: https://issues.apache.org/jira/browse/OPENJPA-1950

[jira] Updated: (OPENJPA-1950) exception when converting datetime2 result from String to java.util.Date (ms sql server)

[ https://issues.apache.org/jira/browse/OPENJPA-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-1950: --- Attachment: OPENJPA-1950-TestCase.zip My own TestCase that shows the problem. > exception when con

[jira] Commented: (OPENJPA-1950) exception when converting datetime2 result from String to java.util.Date (ms sql server)

[ https://issues.apache.org/jira/browse/OPENJPA-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997793#comment-12997793 ] Vermeulen commented on OPENJPA-1950: Oops, I was using an older version of the mssql

[jira] Resolved: (OPENJPA-1950) exception when converting datetime2 result from String to java.util.Date (ms sql server)

[ https://issues.apache.org/jira/browse/OPENJPA-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen resolved OPENJPA-1950. Resolution: Invalid Fix Version/s: 2.1.0 This issue is fixed by using the latest driver fr

[jira] Updated: (OPENJPA-1949) inserting new entities to the front of an existing List fails when using GenerationType.IDENTITY

[ https://issues.apache.org/jira/browse/OPENJPA-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-1949: --- Attachment: OPENJPA-1949-TestCase.zip Reuploaded my TestCase without @author tag and granted ASF li

[jira] Updated: (OPENJPA-1949) inserting new entities to the front of an existing List fails when using GenerationType.IDENTITY

[ https://issues.apache.org/jira/browse/OPENJPA-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-1949: --- Attachment: (was: OPENJPA-1949-TestCase.zip) > inserting new entities to the front of an existi

[jira] Commented: (OPENJPA-1949) inserting new entities to the front of an existing List fails when using GenerationType.IDENTITY

[ https://issues.apache.org/jira/browse/OPENJPA-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998253#comment-12998253 ] Vermeulen commented on OPENJPA-1949: I ran the same test with GenerationType.TABLE a

[jira] [Created] (OPENJPA-1980) cascade merge tries to insert null into id column in a 4 entity structure (no DetachedStateField)

cascade merge tries to insert null into id column in a 4 entity structure (no DetachedStateField) - Key: OPENJPA-1980 URL: https://issues.apache.org/jira/browse/OPENJP

[jira] [Updated] (OPENJPA-1980) cascade merge tries to insert null into id column in a 4 entity structure (no DetachedStateField)

[ https://issues.apache.org/jira/browse/OPENJPA-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-1980: --- Attachment: openjpa-1980-unittest.zip source code with unit test that shows the problem (uses JUnit

[jira] [Updated] (OPENJPA-1980) cascade merge tries to insert null into id column in a 4 entity structure (no DetachedStateField)

[ https://issues.apache.org/jira/browse/OPENJPA-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-1980: --- Description: We use these settings in persistence.xml (useful when entities can be edited by remot

[jira] [Created] (OPENJPA-2239) removing from one List removes all from other List in same entity

Vermeulen created OPENJPA-2239: -- Summary: removing from one List removes all from other List in same entity Key: OPENJPA-2239 URL: https://issues.apache.org/jira/browse/OPENJPA-2239 Project: OpenJPA

[jira] [Commented] (OPENJPA-2239) removing from one List removes all from other List in same entity

[ https://issues.apache.org/jira/browse/OPENJPA-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421266#comment-13421266 ] Vermeulen commented on OPENJPA-2239: Note that OPENJPA-1435 (which is already resolv

[jira] [Updated] (OPENJPA-2239) removing from one List removes all from other List in same entity

[ https://issues.apache.org/jira/browse/OPENJPA-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-2239: --- Attachment: OrderLineRemovalBugTest.java OrderLine.java Order.java

[jira] [Commented] (OPENJPA-2239) removing from one List removes all from other List in same entity

[ https://issues.apache.org/jira/browse/OPENJPA-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13422335#comment-13422335 ] Vermeulen commented on OPENJPA-2239: Personally I would really have liked an excepti

[jira] [Commented] (OPENJPA-2239) removing from one List removes all from other List in same entity

[ https://issues.apache.org/jira/browse/OPENJPA-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13422336#comment-13422336 ] Vermeulen commented on OPENJPA-2239: By the way, my colleague had already noticed th

[jira] [Created] (OPENJPA-2246) when using fetchplans a different entitymanager may incorrectly eagerly fetch a lazy association

Vermeulen created OPENJPA-2246: -- Summary: when using fetchplans a different entitymanager may incorrectly eagerly fetch a lazy association Key: OPENJPA-2246 URL: https://issues.apache.org/jira/browse/OPENJPA-2246

[jira] [Updated] (OPENJPA-2246) when using fetchplans a different entitymanager may incorrectly eagerly fetch a lazy association

[ https://issues.apache.org/jira/browse/OPENJPA-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-2246: --- Attachment: openjpalazyeagerfetchplan.zip Added a complete test case (build with Maven) which shows

[jira] [Created] (OPENJPA-2251) EXISTS with subquery from superclass generates SQL with syntax error

Vermeulen created OPENJPA-2251: -- Summary: EXISTS with subquery from superclass generates SQL with syntax error Key: OPENJPA-2251 URL: https://issues.apache.org/jira/browse/OPENJPA-2251 Project: OpenJPA

[jira] [Commented] (OPENJPA-2251) EXISTS with subquery from superclass generates SQL with syntax error

[ https://issues.apache.org/jira/browse/OPENJPA-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435859#comment-13435859 ] Vermeulen commented on OPENJPA-2251: I just noticed that OPENJPA-658 is not resolved

[jira] [Commented] (OPENJPA-655) Class level query filter

[ https://issues.apache.org/jira/browse/OPENJPA-655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435876#comment-13435876 ] Vermeulen commented on OPENJPA-655: --- Note that the jpasecurity project on sourceforge d

[jira] [Commented] (OPENJPA-2241) Records from a JoinTable being deleted without any related user action

[ https://issues.apache.org/jira/browse/OPENJPA-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435887#comment-13435887 ] Vermeulen commented on OPENJPA-2241: Do you have an entity with two separate mapping

[jira] [Commented] (OPENJPA-2239) removing from one List removes all from other List in same entity

[ https://issues.apache.org/jira/browse/OPENJPA-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13460546#comment-13460546 ] Vermeulen commented on OPENJPA-2239: I had another occurence of this bug which is ev

[jira] [Created] (OPENJPA-2296) N+1 select in eager fetching relation fields of toOne relations

Vermeulen created OPENJPA-2296: -- Summary: N+1 select in eager fetching relation fields of toOne relations Key: OPENJPA-2296 URL: https://issues.apache.org/jira/browse/OPENJPA-2296 Project: OpenJPA

[jira] [Commented] (OPENJPA-2296) N+1 select in eager fetching relation fields of toOne relations

[ https://issues.apache.org/jira/browse/OPENJPA-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493853#comment-13493853 ] Vermeulen commented on OPENJPA-2296: Note that explicitly doing a left join fetch qu

[jira] [Comment Edited] (OPENJPA-2296) N+1 select in eager fetching relation fields of toOne relations

[ https://issues.apache.org/jira/browse/OPENJPA-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493853#comment-13493853 ] Vermeulen edited comment on OPENJPA-2296 at 11/9/12 9:56 AM: -

[jira] [Commented] (OPENJPA-2296) N+1 select in eager fetching relation fields of toOne relations

[ https://issues.apache.org/jira/browse/OPENJPA-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493881#comment-13493881 ] Vermeulen commented on OPENJPA-2296: I found a proof of concept that it IS easily po

[jira] [Commented] (OPENJPA-2296) N+1 select in eager fetching relation fields of toOne relations

[ https://issues.apache.org/jira/browse/OPENJPA-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493917#comment-13493917 ] Vermeulen commented on OPENJPA-2296: Moving up the call stack I see that the eager s

[jira] [Commented] (OPENJPA-2296) N+1 select in eager fetching relation fields of toOne relations

[ https://issues.apache.org/jira/browse/OPENJPA-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493929#comment-13493929 ] Vermeulen commented on OPENJPA-2296: Perhaps the issue can also be summarized as: as

[jira] [Comment Edited] (OPENJPA-2296) N+1 select in eager fetching relation fields of toOne relations

[ https://issues.apache.org/jira/browse/OPENJPA-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493917#comment-13493917 ] Vermeulen edited comment on OPENJPA-2296 at 11/9/12 11:35 AM:

[jira] [Commented] (OPENJPA-1920) N+1 select with entities that contain Maps (even with FetchType.EAGER)

[ https://issues.apache.org/jira/browse/OPENJPA-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493954#comment-13493954 ] Vermeulen commented on OPENJPA-1920: I used the Eclipse debugger which I also used f

[jira] [Comment Edited] (OPENJPA-1920) N+1 select with entities that contain Maps (even with FetchType.EAGER)

[ https://issues.apache.org/jira/browse/OPENJPA-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493954#comment-13493954 ] Vermeulen edited comment on OPENJPA-1920 at 11/9/12 11:54 AM:

[jira] [Comment Edited] (OPENJPA-2296) N+1 select in eager fetching relation fields of toOne relations

[ https://issues.apache.org/jira/browse/OPENJPA-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493917#comment-13493917 ] Vermeulen edited comment on OPENJPA-2296 at 11/9/12 11:57 AM:

[jira] [Updated] (OPENJPA-2296) N+1 select in eager fetching relation fields of toOne relations

[ https://issues.apache.org/jira/browse/OPENJPA-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-2296: --- Attachment: OPENJPA-2296-tests.zip Added test cases that show the bug. > N+1 selec

[jira] [Comment Edited] (OPENJPA-2296) N+1 select in eager fetching relation fields of toOne relations

[ https://issues.apache.org/jira/browse/OPENJPA-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496328#comment-13496328 ] Vermeulen edited comment on OPENJPA-2296 at 11/13/12 5:03 PM:

[jira] [Comment Edited] (OPENJPA-2296) N+1 select in eager fetching relation fields of toOne relations

[ https://issues.apache.org/jira/browse/OPENJPA-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496328#comment-13496328 ] Vermeulen edited comment on OPENJPA-2296 at 11/13/12 5:20 PM:

[jira] [Updated] (OPENJPA-2296) N+1 select in eager fetching relation fields of toOne relations

[ https://issues.apache.org/jira/browse/OPENJPA-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-2296: --- Description: EDIT: the N+1 select problem also always occurs when eagerly fetching a ManyToOne fie

[jira] [Updated] (OPENJPA-2296) N+1 select problems when eager fetching OneToOne and ManyToOne fields

[ https://issues.apache.org/jira/browse/OPENJPA-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-2296: --- Summary: N+1 select problems when eager fetching OneToOne and ManyToOne fields (was: N+1 select in

[jira] [Commented] (OPENJPA-2296) N+1 select problems when eager fetching OneToOne and ManyToOne fields

[ https://issues.apache.org/jira/browse/OPENJPA-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496936#comment-13496936 ] Vermeulen commented on OPENJPA-2296: I think I have done all I possibly can to help

[jira] [Updated] (OPENJPA-1920) N+1 select with entities that contain Maps (even with FetchType.EAGER)

[ https://issues.apache.org/jira/browse/OPENJPA-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-1920: --- Attachment: testeagermapfetching.zip Added OpenJPA unit tests that show the problem. Also added a t

[jira] [Updated] (OPENJPA-2296) N+1 select problems when eager fetching OneToOne and ManyToOne fields

[ https://issues.apache.org/jira/browse/OPENJPA-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-2296: --- Description: EDIT: - the N+1 select problem also always occurs when eagerly fetching a ManyToOne

[jira] [Updated] (OPENJPA-2296) N+1 select problems when eager fetching OneToOne and ManyToOne fields

[ https://issues.apache.org/jira/browse/OPENJPA-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-2296: --- Description: EDIT: - the N+1 select problem also always occurs when eagerly fetching a ManyToOne

[jira] [Updated] (OPENJPA-2296) N+1 select problems when eager fetching OneToOne and ManyToOne fields

[ https://issues.apache.org/jira/browse/OPENJPA-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-2296: --- Attachment: OPENJPA-2296-tests.zip Fixed an error in ManyBToOneA test. Added an Order ManyToOne Cu

[jira] [Updated] (OPENJPA-2296) N+1 select problems when eager fetching OneToOne and ManyToOne fields

[ https://issues.apache.org/jira/browse/OPENJPA-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-2296: --- Attachment: (was: OPENJPA-2296-tests.zip) > N+1 select problems when eager fetching OneToOn

[jira] [Updated] (OPENJPA-2296) N+1 select problems when eager fetching OneToOne and ManyToOne fields

[ https://issues.apache.org/jira/browse/OPENJPA-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-2296: --- Description: EDIT: - an N+1 select problem also always occurs when eagerly fetching a ManyToOne

[jira] [Commented] (OPENJPA-2296) N+1 select problems when eager fetching OneToOne and ManyToOne fields

[ https://issues.apache.org/jira/browse/OPENJPA-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13497953#comment-13497953 ] Vermeulen commented on OPENJPA-2296: Perhaps the problem with bidirectional can be s

[jira] [Commented] (OPENJPA-2296) N+1 select problems when eager fetching OneToOne and ManyToOne fields

[ https://issues.apache.org/jira/browse/OPENJPA-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13497971#comment-13497971 ] Vermeulen commented on OPENJPA-2296: I also tested the simple Order - Customer examp

[jira] [Commented] (OPENJPA-134) Extra unneeded SQL joins for OneToMany relationship with fetch type EAGER

[ https://issues.apache.org/jira/browse/OPENJPA-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500920#comment-13500920 ] Vermeulen commented on OPENJPA-134: --- Unfortunately for the above eager bidirectional Or

[jira] [Commented] (OPENJPA-2296) N+1 select problems when eager fetching OneToOne and ManyToOne fields

[ https://issues.apache.org/jira/browse/OPENJPA-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500937#comment-13500937 ] Vermeulen commented on OPENJPA-2296: - For the bidirectional ManyBToOneA, using @Ea

[jira] [Created] (OPENJPA-2299) N+1 select when eager fetching two collection fields of the same entity type

Vermeulen created OPENJPA-2299: -- Summary: N+1 select when eager fetching two collection fields of the same entity type Key: OPENJPA-2299 URL: https://issues.apache.org/jira/browse/OPENJPA-2299 Project: O

[jira] [Updated] (OPENJPA-2299) N+1 select when eager fetching two collection fields of the same entity type

[ https://issues.apache.org/jira/browse/OPENJPA-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-2299: --- Attachment: OPENJPA-2299-tests.zip Added an OpenJPA test case which shows the problem.

[jira] [Created] (OPENJPA-2311) JPA cannot handle @OneToMany with @OrderColumn and non-nullable @JoinColumn with foreign key constraint

Vermeulen created OPENJPA-2311: -- Summary: JPA cannot handle @OneToMany with @OrderColumn and non-nullable @JoinColumn with foreign key constraint Key: OPENJPA-2311 URL: https://issues.apache.org/jira/browse/OPENJPA-2

[jira] [Updated] (OPENJPA-2311) JPA cannot handle @OneToMany with @OrderColumn and non-nullable @JoinColumn with foreign key constraint

[ https://issues.apache.org/jira/browse/OPENJPA-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-2311: --- Attachment: TestOrderColumnOpenJPA2311.java Added a unit test based on TestOrderColumn that reprodu

[jira] [Updated] (OPENJPA-2311) JPA cannot handle @OneToMany with @OrderColumn and non-nullable @JoinColumn with foreign key constraint

[ https://issues.apache.org/jira/browse/OPENJPA-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-2311: --- Description: Situation: an ordered List whose entities are completely owned by the parent entity b

[jira] [Created] (OPENJPA-2375) generate predictable names for primary and foreign keys

Vermeulen created OPENJPA-2375: -- Summary: generate predictable names for primary and foreign keys Key: OPENJPA-2375 URL: https://issues.apache.org/jira/browse/OPENJPA-2375 Project: OpenJPA Issue

[jira] [Commented] (OPENJPA-2375) generate predictable names for primary and foreign keys

[ https://issues.apache.org/jira/browse/OPENJPA-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13640343#comment-13640343 ] Vermeulen commented on OPENJPA-2375: Here's what I already tried: The most obvious

[jira] [Updated] (OPENJPA-2375) generate predictable names for primary and foreign keys

[ https://issues.apache.org/jira/browse/OPENJPA-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-2375: --- Description: When the MappingTool creates the database schema, OpenJPA will let the database deter

[jira] [Commented] (OPENJPA-2318) Left outer join is not generated when specifien using Criteria API

[ https://issues.apache.org/jira/browse/OPENJPA-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13658240#comment-13658240 ] Vermeulen commented on OPENJPA-2318: I'm having exacly the same issue. When printing

[jira] [Commented] (OPENJPA-2318) Left outer join is not generated when specifien using Criteria API

[ https://issues.apache.org/jira/browse/OPENJPA-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13658248#comment-13658248 ] Vermeulen commented on OPENJPA-2318: Not 100% sure but this may have to do with inhe

[jira] [Commented] (OPENJPA-2318) Left outer join is not generated when specifien using Criteria API

[ https://issues.apache.org/jira/browse/OPENJPA-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13658255#comment-13658255 ] Vermeulen commented on OPENJPA-2318: Same issue when leaving out Category and making

[jira] [Commented] (OPENJPA-2318) Left outer join is not generated when specifien using Criteria API

[ https://issues.apache.org/jira/browse/OPENJPA-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13658265#comment-13658265 ] Vermeulen commented on OPENJPA-2318: I reproduced the problem for another query with

[jira] [Commented] (OPENJPA-2318) Left outer join is not generated when specifien using Criteria API

[ https://issues.apache.org/jira/browse/OPENJPA-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13658292#comment-13658292 ] Vermeulen commented on OPENJPA-2318: I created an (almost) official OpenJPA test cas

[jira] [Commented] (OPENJPA-2318) Left outer join is not generated when specifien using Criteria API

[ https://issues.apache.org/jira/browse/OPENJPA-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13658316#comment-13658316 ] Vermeulen commented on OPENJPA-2318: I found the cause of the problem! By simply fo

[jira] [Commented] (OPENJPA-2318) Left outer join is not generated when specifien using Criteria API

[ https://issues.apache.org/jira/browse/OPENJPA-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13658316#comment-13658316 ] Vermeulen commented on OPENJPA-2318: I found the cause of the problem! By simply fo

[jira] [Comment Edited] (OPENJPA-2317) Criteria API doesn' generate LEFT OUTER JOIN in subquery as expected

[ https://issues.apache.org/jira/browse/OPENJPA-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13658329#comment-13658329 ] Vermeulen edited comment on OPENJPA-2317 at 5/15/13 2:01 PM: -

[jira] [Commented] (OPENJPA-2296) N+1 select problems when eager fetching OneToOne and ManyToOne fields

[ https://issues.apache.org/jira/browse/OPENJPA-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750180#comment-13750180 ] Vermeulen commented on OPENJPA-2296: [~jgogstad] The workaround I use is: turn on TR

[jira] [Commented] (OPENJPA-1991) Support ROW_NUMBER pagination on MS SQL Server 2005

[ https://issues.apache.org/jira/browse/OPENJPA-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13786149#comment-13786149 ] Vermeulen commented on OPENJPA-1991: This definitely has my vote. When I use setMaxR

[jira] [Issue Comment Deleted] (OPENJPA-1991) Support ROW_NUMBER pagination on MS SQL Server 2005

[ https://issues.apache.org/jira/browse/OPENJPA-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-1991: --- Comment: was deleted (was: This definitely has my vote. When I use setMaxResults the generated SQL

[jira] [Commented] (OPENJPA-1980) cascade merge tries to insert null into id column in a 4 entity structure (no DetachedStateField)

[ https://issues.apache.org/jira/browse/OPENJPA-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13879819#comment-13879819 ] Vermeulen commented on OPENJPA-1980: I removed my workaround code and ran my tests a

[jira] [Commented] (OPENJPA-1950) exception when converting datetime2 result from String to java.util.Date (ms sql server)

[ https://issues.apache.org/jira/browse/OPENJPA-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885233#comment-13885233 ] Vermeulen commented on OPENJPA-1950: Today I tried out the jtds driver 1.3.1 instead

[jira] [Commented] (OPENJPA-1966) Entity graphs containing bi-directional references may not merge correctly if an entity does not contain a state manager

[ https://issues.apache.org/jira/browse/OPENJPA-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14027797#comment-14027797 ] Vermeulen commented on OPENJPA-1966: Perhaps the following is related so I am adding

[jira] [Commented] (OPENJPA-2299) N+1 select when eager fetching two collection fields of the same entity type

[ https://issues.apache.org/jira/browse/OPENJPA-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14068305#comment-14068305 ] Vermeulen commented on OPENJPA-2299: I did find a (brittle) workaround for this issu

[jira] [Comment Edited] (OPENJPA-2299) N+1 select when eager fetching two collection fields of the same entity type

[ https://issues.apache.org/jira/browse/OPENJPA-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14068305#comment-14068305 ] Vermeulen edited comment on OPENJPA-2299 at 7/21/14 8:07 AM: -

[jira] [Created] (OPENJPA-2540) merge without DetachedStateField deletes lazy fields in embedded entities

Vermeulen created OPENJPA-2540: -- Summary: merge without DetachedStateField deletes lazy fields in embedded entities Key: OPENJPA-2540 URL: https://issues.apache.org/jira/browse/OPENJPA-2540 Project: Open

[jira] [Updated] (OPENJPA-2540) merge without DetachedStateField deletes lazy fields in embedded entities

[ https://issues.apache.org/jira/browse/OPENJPA-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-2540: --- Attachment: TestEmbeddable.java LazyFieldsInEmbeddedEntityTest.java L

[jira] [Updated] (OPENJPA-2540) merge without DetachedStateField deletes lazy fields in embedded entities

[ https://issues.apache.org/jira/browse/OPENJPA-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-2540: --- Description: I am using the setting Like the summary says, I have an embedded entity with a field

[jira] [Updated] (OPENJPA-2540) merge without DetachedStateField deletes lazy fields in embedded entities

[ https://issues.apache.org/jira/browse/OPENJPA-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-2540: --- Priority: Critical (was: Major) I increased the priority. I just found a dramatic consequence by ch

[jira] [Comment Edited] (OPENJPA-2540) merge without DetachedStateField deletes lazy fields in embedded entities

[ https://issues.apache.org/jira/browse/OPENJPA-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14182688#comment-14182688 ] Vermeulen edited comment on OPENJPA-2540 at 10/24/14 11:51 AM: ---

[jira] [Commented] (OPENJPA-2540) merge without DetachedStateField deletes lazy fields in embedded entities

[ https://issues.apache.org/jira/browse/OPENJPA-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185250#comment-14185250 ] Vermeulen commented on OPENJPA-2540: Thank you for looking into it. A simple workaro

[jira] [Created] (OPENJPA-2559) OpenJPA silently ignores assigning a null value to a non-nullable column

Vermeulen created OPENJPA-2559: -- Summary: OpenJPA silently ignores assigning a null value to a non-nullable column Key: OPENJPA-2559 URL: https://issues.apache.org/jira/browse/OPENJPA-2559 Project: OpenJ

[jira] [Updated] (OPENJPA-2559) OpenJPA silently ignores assigning a null value to a non-nullable column

[ https://issues.apache.org/jira/browse/OPENJPA-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vermeulen updated OPENJPA-2559: --- Attachment: NonNullableColumnTest.java NonNullable.java Added a simple test case whi

[jira] [Commented] (OPENJPA-2559) OpenJPA silently ignores assigning a null value to a non-nullable column

[ https://issues.apache.org/jira/browse/OPENJPA-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14275209#comment-14275209 ] Vermeulen commented on OPENJPA-2559: May be the same issue as OPENJPA-665 that was a

[jira] [Commented] (OPENJPA-2559) OpenJPA silently ignores assigning a null value to a non-nullable column

[ https://issues.apache.org/jira/browse/OPENJPA-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14275214#comment-14275214 ] Vermeulen commented on OPENJPA-2559: Indeed the description of the duplicated issue

[jira] [Commented] (OPENJPA-2559) OpenJPA silently ignores assigning a null value to a non-nullable column

[ https://issues.apache.org/jira/browse/OPENJPA-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14275228#comment-14275228 ] Vermeulen commented on OPENJPA-2559: As mentioned on the openjpa-dev mailing list, @

[jira] [Comment Edited] (OPENJPA-2559) OpenJPA silently ignores assigning a null value to a non-nullable column

[ https://issues.apache.org/jira/browse/OPENJPA-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14275228#comment-14275228 ] Vermeulen edited comment on OPENJPA-2559 at 1/13/15 2:23 PM: -

  1   2   >