When using NOT NULL constraint on foreign key it is not possible to use
CascadeType.ALL and GeneratedId
---
Key: OPENJPA-177
URL: https://issues.apache.org/jira/br
In the case above, another webapp has loaded the forums module,
causing this
webapp to look for the mappings in that module even though they aren't
available.
I had difficulty trying to figure out how to restrict which
subclasses are
'seen'. Ideally I think it'd be done in the
MetaDataRepos
[
https://issues.apache.org/jira/browse/OPENJPA-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482815
]
Abe White commented on OPENJPA-177:
---
OpenJPA will insert records in the order that you persist the corresponding
[
https://issues.apache.org/jira/browse/OPENJPA-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482821
]
Abe White commented on OPENJPA-175:
---
I'll have to see the code in context once it's checked in because I'm not ver
[
https://issues.apache.org/jira/browse/OPENJPA-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux reassigned OPENJPA-89:
-
Assignee: Marc Prud'hommeaux
> Bulk delete fails to delete owned many-to-many rel
[
https://issues.apache.org/jira/browse/OPENJPA-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux reassigned OPENJPA-135:
--
Assignee: Marc Prud'hommeaux
> join fetch not returning duplicate references w
[
https://issues.apache.org/jira/browse/OPENJPA-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482904
]
Abe White commented on OPENJPA-168:
---
> The reason for using -1 is that we want to differentiate between cases wher
Hi,
Now that OpenJPA is maturing into a well-rounded community with lots
of users as well as developers, I think it's time we start thinking
about formalizing a roadmap for the project.
Patrick did a great job in looking at all the JIRA issues and
proposing release numbers that the issues
[
https://issues.apache.org/jira/browse/OPENJPA-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482926
]
Ritika Maheshwari commented on OPENJPA-168:
---
based on your latest comments here is another patch OPENJPA-
[
https://issues.apache.org/jira/browse/OPENJPA-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ritika Maheshwari updated OPENJPA-168:
--
Attachment: OPENJPA-168.patch2.txt
> sql optimize n rows query hint
>
[
https://issues.apache.org/jira/browse/OPENJPA-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482931
]
Abe White commented on OPENJPA-175:
---
1. Are you also going to fix InExpression to honor the DBDictionary's new in
[
https://issues.apache.org/jira/browse/OPENJPA-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srinivasa updated OPENJPA-175:
--
1 - Yes, was planning to do it as a separate JIRA given that it directly does
not concern the issue raise
in the spirit of "do-ocracy" I'll put together a straw proposal and
see where it goes from here.
+1 :)
I do think that it would be good to keep as much structured
information as possible in JIRA (their "Roadmap Panel" is pretty
nice), but some additional over-arching exposition might be
Abe White wrote:
>
>> In the case above, another webapp has loaded the forums module,
>> causing this
>> webapp to look for the mappings in that module even though they aren't
>> available.
>>
>> I had difficulty trying to figure out how to restrict which
>> subclasses are
>> 'seen'. Ideall
Handle case-sensitive databases - inappropriate change of field case to
uppercase
-
Key: OPENJPA-178
URL: https://issues.apache.org/jira/browse/OPENJPA-178
Project: OpenJ
[
https://issues.apache.org/jira/browse/OPENJPA-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srinivasa updated OPENJPA-175:
--
Attachment: InExpression-Diff.txt
> Eager selects by PagingResultObjectProvider may not use the FetchB
16 matches
Mail list logo