On Mar 1, 2007, at 11:01 AM, Patrick Linskey wrote:
The diff email didn't include enough context for you. This is in the
createContainerEntityManagerFactory() method. It's my contention that
createContainerEntityManagerFactory() will only be invoked by things
that intend to close resources prop
> Can you ask OpenJPA to quote ALL identifiers for a particular
> data source?
Not currently, but certainly would be useful once we add quoting
support.
> You might have an identifier (with some databases) that is
> declared as "a", but if you access it without quotes in a query
> it will be aut
Patrick,
Can you ask OpenJPA to quote ALL identifiers for a particular
data source?
You might have an identifier (with some databases) that is
declared as "a", but if you access it without quotes in a query
it will be auto-uppercased to A and won't match.
Rather than a special case for SQL rese
Thanks for all the feedback, let me remove the @Version (it should really be
a basic field instead as it's app specific) and test it again.
On 3/1/07, Patrick Linskey <[EMAIL PROTECTED]> wrote:
> Here is a link to the source (and no version field):
There is a version field in there. How are yo
The diff email didn't include enough context for you. This is in the
createContainerEntityManagerFactory() method. It's my contention that
createContainerEntityManagerFactory() will only be invoked by things
that intend to close resources properly.
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
On Mar 1, 2007, at 7:55 AM, Patrick Linskey wrote:
My understanding is that "Fix Version(s)" captures both the version
that
something is scheduled to be fixed in (for unresolved issues) and the
version that something actually was fixed in (for resolved issues).
"Affected Version(s)" identifi
Hi Patrick,
I'm trying to understand how the code knows it's running in an
appserver environment...
Thanks,
Craig
On Mar 1, 2007, at 7:52 AM, Patrick Linskey wrote:
The difference is that in an appserver environment, this will return a
non-finalizing EM by default, but in a Java SE enviro
[
https://issues.apache.org/jira/browse/OPENJPA-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477043
]
Craig Russell commented on OPENJPA-20:
--
I agree with Marc that it's a bug in the doc. The doc could also be rewo
Hi Pinaki,
On Feb 26, 2007, at 10:01 AM, Pinaki Poddar wrote:
Respected Sir,
Sorry to disagree. If you fetch Department instances, I think you
always want the _employees collection to contain all the related
Employees.
You never want a filtered collection unless you provide a filter
via s
BTW, sorry about all the emails. Halfway through my bulk changes, I
realized that I could turn off email spam for bulk changes.
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
___
Notice: This email message, together with any a
Patrick,
Sounds good. I like the aggressive schedule idea. I hope we can pull it
off... :-)
Kevin
On 3/1/07, Patrick Linskey <[EMAIL PROTECTED]> wrote:
My understanding is that "Fix Version(s)" captures both the version that
something is scheduled to be fixed in (for unresolved issues) and
My understanding is that "Fix Version(s)" captures both the version that
something is scheduled to be fixed in (for unresolved issues) and the
version that something actually was fixed in (for resolved issues).
"Affected Version(s)" identifies the versions that the issue is present
in.
So, I spen
The difference is that in an appserver environment, this will return a
non-finalizing EM by default, but in a Java SE environment, it will
return a finalizing EM by default. See the last bit of my last comment
in OPENJPA-160.
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
__
> Here is a link to the source (and no version field):
There is a version field in there. How are you invoking the non-default
constructor? As Abe mentioned, if your version field is set to a value
other than the Java default (0 in this case), OpenJPA will assume that
the instance is detached.
-P
If you set the version field of an instance to a non-default value,
OpenJPA assumes the instance was detached, or that you're actively
trying to make it behave as a detached instance.
___
Notice: This email message, together
Patrick,
I'm a little confused with all of these updates you are doing with the JIRA
Issues. Most of the updates are related to specifying a Fix Version of
0.9.7. Does this mean you are planning on having all of these Issues
resolved for 0.9.7? Or, do you think this field specifies which versio
[
https://issues.apache.org/jira/browse/OPENJPA-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux resolved OPENJPA-23.
---
Resolution: Fixed
Assignee: Marc Prud'hommeaux
I am fairly certain this was fix
17 matches
Mail list logo
