William-
I don't know how you specify collation, but if it is expressible via
the column type name, you could always set the "type-name" of the
column in the schema file (e.g., setting the type-name to be "VARCHAR
WITH ASCII COLLATION").
If it needs to be specific in the "CREATE TABLE" pa
Marc,
In SQL Server, we specify Collation with below code. Therefore, we can't set
the option in "type-name". In our project, there are hundreds of columns
need case-sensitive collation support. It's really painful to set all of
them in generated script. The best solution is custom SQLServerDictio
William-
If you wanted to have all your varchar columns be specified as
"varchar(SIZE) COLLATE French_CI_AS", you could specify the property:
openjpa.jdbc.DBDictionary: VarcharTypeName="varchar{0} COLLATE
French_CI_AS"
On Jan 31, 2007, at 12:39 AM, William Cai wrote:
Marc,
In SQL
Wow~~~ You're the man, Marc! The problem is resolved!
On 1/31/07, Marc Prud'hommeaux <[EMAIL PROTECTED]> wrote:
William-
If you wanted to have all your varchar columns be specified as
"varchar(SIZE) COLLATE French_CI_AS", you could specify the property:
openjpa.jdbc.DBDictionary: VarcharT
Hello,
the request from Pinaki regarding the transactionlistener also are in our
business need. The actual possibility of Transactionlistener API are to small
in OPEN-JPA/Kodo. It would be great when the folloing apsects could be
considered.
1. Why could the Transactionlister not have the same
> 1. Why could the Transactionlister not have the same
> structure of API as the Instancelifecycle Listener. That mean
> configuring a Default Transactionlister with the
> brokerfactory, reading actual transactionlistener's in the
> broker and manipulating actual transactionlisterners (that
>
Hello Abe,
in our use Case we need the Transactionlister to implement an audit-log on
PC-Object and PC-Object-Attributelevel. Because were a building a
item/masterdata-Management-system. One of the main targets is to track every
change on the Masterdata and then to export the Change to over 100
Craig,
If anybody would have a channel to the CTS team, I would think it would be
you. :-) I have also passed on this request to our CTS rep to see where it
takes us. Good idea. Thanks.
Kevin
On 1/30/07, Craig L Russell <[EMAIL PROTECTED]> wrote:
Hi Kevin,
I agree with your analysis.
I wo
Another possibility is that you need to explicitly declare the classes that
you want processed for automatic table creation via the ..
elements. Scanning for available Entity classes won't work when attempting
to auto create the tables.
Kevin
On 1/30/07, Marc Prud'hommeaux <[EMAIL PROTECTED]> w
AutoDetach property has no effect
-
Key: OPENJPA-118
URL: https://issues.apache.org/jira/browse/OPENJPA-118
Project: OpenJPA
Issue Type: Bug
Components: lib
Environment: Java SE
[
https://issues.apache.org/jira/browse/OPENJPA-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Ezzio updated OPENJPA-118:
Attachment: TestFixesForOpenJPA-118.zip
Tests and fixes for the bug. Not sure if the tests are in
[
https://issues.apache.org/jira/browse/OPENJPA-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469093
]
Pinaki Poddar commented on OPENJPA-117:
---
> Adding listeners should generally either be done as an initializati
Basically, if we have dirtied the Persistence Context, then do a
flush()
followed by the detachAllInternal(). I don't think the clear()
should be
doing this flush() operation. Any disagreement?
I agree. But note that just removing the flush call won't work for a
couple of reasons: it's
Understood, Abe. I just wanted to get some agreement with you and/or
Patrick before pursuing this type of change. Thanks!
Kevin
On 1/31/07, Abe White <[EMAIL PROTECTED]> wrote:
> Basically, if we have dirtied the Persistence Context, then do a
> flush()
> followed by the detachAllInternal().
[
https://issues.apache.org/jira/browse/OPENJPA-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469123
]
Patrick Linskey commented on OPENJPA-93:
Has anyone tested this on non-WLS appservers?
> Sequence generation
[
https://issues.apache.org/jira/browse/OPENJPA-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469126
]
Patrick Linskey commented on OPENJPA-118:
-
Sadly, due to some maven environment issues, all tests that need
This commit is way too big for its changes.
I recommend that everyone do an svn diff prior to commit to make sure
that you don't have a line-end problem, such as this appears to have.
Craig
On Jan 31, 2007, at 11:27 AM, [EMAIL PROTECTED] wrote:
Author: kwsutter
Date: Wed Jan 31 11:27:11 20
I'd prefer to see a separate test that tests all of the em methods
that are supposed to throw an exception (all of them except isOpen
and getTransaction). Putting this new test here is awkward.
Craig
On Jan 31, 2007, at 11:27 AM, [EMAIL PROTECTED] wrote:
Author: kwsutter
Date: Wed Jan 31 1
Yeah, I tend to agree. Just wanted to get something out there for the fix
that was provided... And, doing it this way allows me to experiment more
with getting these line ending characters correct... :-) JK!
On 1/31/07, Craig L Russell <[EMAIL PROTECTED]> wrote:
I'd prefer to see a separate
What version of OpenJPA will this be in and did dropTable get
implemented?
-dain
On Jan 2, 2007, at 6:50 PM, Patrick Linskey wrote:
-Original Message-
From: Shay Banon [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 02, 2007 2:33 PM
To: open-jpa-dev@incubator.apache.org
Subject: RE:
I seem to recall deciding to not use the SVN eclipse integration a few
months ago -- I do all my svn work from the command line. Maybe this was
why I made that decision.
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
___
Notice
Hi Kevin,
Sorry for commenting before reading this...
On Jan 31, 2007, at 11:39 AM, Kevin Sutter wrote:
Sorry about the "whole changed file" thing again. I thought I had
found the
problem with a doubly defined [miscellany] section in my svn config
file.
But, I changed that and I still have
It's in 0.9.7-snapshot; I don't remember the change number.
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
___
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its su
[
https://issues.apache.org/jira/browse/OPENJPA-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey resolved OPENJPA-94.
Resolution: Fixed
> Allow MappingTool and persistence.xml to support drop-create for databa
I'm dumb. I thought I was using hsqldb in memory only mode, but
instead it was in file mode.
-dain
On Jan 31, 2007, at 6:33 AM, Kevin Sutter wrote:
Another possibility is that you need to explicitly declare the
classes that
you want processed for automatic table creation via the ..class>
e
[
https://issues.apache.org/jira/browse/OPENJPA-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux resolved OPENJPA-118.
Resolution: Fixed
I've corrected a couple minior problems with the patch (no ASF l
EntityManager.clear() should not implicitly invoke the flush operation
--
Key: OPENJPA-119
URL: https://issues.apache.org/jira/browse/OPENJPA-119
Project: OpenJPA
Issue Type
FYI, the indexing finished finally (their settings for the Apache
repositories are very slow so that they don't unnecessarily load down
the servers).
You can see the up-to-date index at:
http://fisheye3.cenqua.com/changelog/openjpa/
On Jan 24, 2007, at 9:12 AM, Patrick Linskey wrote
[
https://issues.apache.org/jira/browse/OPENJPA-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Wisneski closed OPENJPA-16.
-
Resolution: Fixed
This problem has been fixed
> NPE in createQuery for EJB QL with nested correl
[
https://issues.apache.org/jira/browse/OPENJPA-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Wisneski closed OPENJPA-27.
-
Resolution: Duplicate
duplicate of OPENJPA-22
> SQL Parameter markers generated for literals cau
[
https://issues.apache.org/jira/browse/OPENJPA-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Wisneski closed OPENJPA-52.
-
Resolution: Duplicate
duplicate of OPENJPA-28
> bad sql pushdown, puts group by in outer select
[
https://issues.apache.org/jira/browse/OPENJPA-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Wisneski closed OPENJPA-47.
-
Resolution: Duplicate
duplicate of OPENJPA-26
> 143 arithmetic unary operator (+,-) gives parsin
[
https://issues.apache.org/jira/browse/OPENJPA-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Wisneski closed OPENJPA-45.
-
Resolution: Duplicate
duplicate of OPENJPA-49
> pushdown sql uses outer join when it should use
[
https://issues.apache.org/jira/browse/OPENJPA-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Wisneski closed OPENJPA-56.
-
Resolution: Fixed
already fixed in latest code
> in derby concat with input parameter needs a ca
[
https://issues.apache.org/jira/browse/OPENJPA-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Wisneski closed OPENJPA-53.
-
Resolution: Fixed
not a problem anymore
> bad sql pushdown for nested subselects, missing neste
[
https://issues.apache.org/jira/browse/OPENJPA-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Wisneski closed OPENJPA-54.
-
Resolution: Fixed
already fixed
> bad sql pushdown, should use all syntax
>
[
https://issues.apache.org/jira/browse/OPENJPA-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Wisneski closed OPENJPA-25.
-
Resolution: Fixed
not a problem anymore
> Incorrect SQL generated for queries involving more tha
[
https://issues.apache.org/jira/browse/OPENJPA-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Wisneski closed OPENJPA-55.
-
Resolution: Fixed
fixed by revision 497605
> Allow executeUpdate() invocations on native queries
[
https://issues.apache.org/jira/browse/OPENJPA-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Wisneski closed OPENJPA-48.
-
Resolution: Fixed
fixed in recent code
> parsing error - cast of subselect does not work
>
[
https://issues.apache.org/jira/browse/OPENJPA-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Wisneski closed OPENJPA-50.
-
Resolution: Fixed
fixed in recent code
> bad sql pushdown, cast changes datatype
> -
For Multi Table Entity subselect with field in second table gets DB2 SQL error:
SQLCODE: -104, SQLSTATE: 42601
--
Key: OPENJPA-120
URL: https://issues.apac
Table name defaults to the class name instead of the entity name
Key: OPENJPA-121
URL: https://issues.apache.org/jira/browse/OPENJPA-121
Project: OpenJPA
Issue Type: Bug
[
https://issues.apache.org/jira/browse/OPENJPA-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Wisneski closed OPENJPA-110.
--
Resolution: Fixed
already fixed in current code
> Every NamedNativeQuery using ResultSetMappi
[
https://issues.apache.org/jira/browse/OPENJPA-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Wisneski closed OPENJPA-62.
-
Resolution: Fixed
fixed in recent code
> Ejbql join queries show invalid null Entities when run
EntityManager does not throw exceptions after close() in required cases
---
Key: OPENJPA-122
URL: https://issues.apache.org/jira/browse/OPENJPA-122
Project: OpenJPA
Issue Ty
[
https://issues.apache.org/jira/browse/OPENJPA-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Russell updated OPENJPA-122:
--
Attachment: TestEntityManagerMethodsThrowAfterClose.java
This test cannot be checked in until
[
https://issues.apache.org/jira/browse/OPENJPA-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Russell updated OPENJPA-122:
--
Attachment: EntityManagerImpl.patch.txt
Please review this patch.
This patch fixes the issue
[
https://issues.apache.org/jira/browse/OPENJPA-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey resolved OPENJPA-10.
Resolution: Fixed
> persistence unit name should be default diagnostic context for standard
[
https://issues.apache.org/jira/browse/OPENJPA-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469345
]
Patrick Linskey commented on OPENJPA-10:
Resolved with 475084
> persistence unit name should be default diag
[
https://issues.apache.org/jira/browse/OPENJPA-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey resolved OPENJPA-36.
Resolution: Fixed
> Add cwiki url to incubator status page
> --
[
https://issues.apache.org/jira/browse/OPENJPA-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469346
]
Patrick Linskey commented on OPENJPA-36:
Resolved with Marc's synchronization between the wiki and the site.
[
https://issues.apache.org/jira/browse/OPENJPA-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey resolved OPENJPA-40.
Resolution: Fixed
> Testing OpenJPA and Spring integration fails
>
[
https://issues.apache.org/jira/browse/OPENJPA-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469347
]
Patrick Linskey commented on OPENJPA-40:
To my knowledge, this has been resolved.
> Testing OpenJPA and Spri
Test framework should allow tests that are expected to fail to be checked in
Key: OPENJPA-123
URL: https://issues.apache.org/jira/browse/OPENJPA-123
Project: OpenJPA
[
https://issues.apache.org/jira/browse/OPENJPA-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-123:
Priority: Major
> Test framework should allow tests that are expected to fail to be checke
[
https://issues.apache.org/jira/browse/OPENJPA-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469355
]
Patrick Linskey commented on OPENJPA-123:
-
OPENJPA-122 is an example of a test case that should have been co
56 matches
Mail list logo