Granted, but with a reasonable implementation the cost should be
low for:
"at commit / flush time compare the current values with the original values
to figure out what to write back to the database."
If you are going to issue "tuned" updates to the DB, determining
what "really" changed (as oppo
ry, copyrighted and/or legally
> privileged, and is intended solely for the use of the
> individual or entity named in this message. If you are not
> the intended recipient, and have received this message in
> error, please immediately return this by email and then delete it.
Ok, this sounds good.
> -Original Message-
> From: Abe White [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 5 April 2007 2:29 a.m.
> To: open-jpa-dev@incubator.apache.org
> Subject: Re: Forced getter/setter access
>
>
> > I meant "tuned" as in not including columns in the SQL update "set"
Is this a combination of Gavin King and Mike Keith, or something even more
scary?
> -Original Message-
> From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED]
> Sent: Monday, 7 May 2007 12:53 p.m.
> To: open-jpa-dev@incubator.apache.org
> Subject: Re: [VOTE] Graduate from Incubation
>
>
>
Folks,
I am exploring the idea of using OpenJPA internal APIs to obtain
meta-data from a persistence unit (e.g. JAR) for use in custom
code generation.
Since I'm a bit of a newbie to OpenJPA, it would be helpful if
someone could give me some starting pointers to save me a little
time.
Suppose I
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
[
https://issues.apache.org/jira/browse/OPENJPA-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474846
]
Evan Ireland commented on OPENJPA-125:
--
I would recommend an XML schema that permits properties (e.g. sets of
