[
https://issues.apache.org/jira/browse/OPENJPA-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey closed OPENJPA-431.
---
Resolution: Invalid
Closing on the assumption that setting the 'openjpa.jdbc.SchemaFactory'
[
https://issues.apache.org/jira/browse/OPENJPA-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-432:
Priority: Major (was: Minor)
> Would like for OpenJPA to provide a platform for eclipse D
[
https://issues.apache.org/jira/browse/OPENJPA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey closed OPENJPA-433.
---
Resolution: Invalid
This is actually intentional, and can be controlled via the DatePrecisio
Setting a null value for a primitive type field in a query results in hang
--
Key: OPENJPA-434
URL: https://issues.apache.org/jira/browse/OPENJPA-434
Project: OpenJPA
Is
Timestamp rounded upon database updating
Key: OPENJPA-433
URL: https://issues.apache.org/jira/browse/OPENJPA-433
Project: OpenJPA
Issue Type: Bug
Components: sql
Affects Versions: 1.0.0
JPA TCK ran successfully against Derby and DB2.
Albert Lee.
On 11/5/07, Albert Lee <[EMAIL PROTECTED]> wrote:
>
> I had another team member, who has access to the TCK license, ran the TCK
> before OPENJPA-370 is removed. I plan to do the same for this release
> candidate.
>
> If you can also giv
On Nov 5, 2007, at 9:25 PM, Craig L Russell wrote:
I think one of the confusions here is that there are two ways to
map relationships using a join table from the side that has a
unique column in the join table.
You can consider the table as a secondary table, in which there is
at most on
I think one of the confusions here is that there are two ways to map
relationships using a join table from the side that has a unique
column in the join table.
You can consider the table as a secondary table, in which there is at
most one row in the join table for each row in the main table
Right. But without mappedBy, it's not a backpointer, but another unidirectional
relationship.
-marina
Patrick Linskey wrote:
I think he's actually trying to just have a single (unidirectional)
reference -- I think he added the backpointer just to see if he could
get things working that way.
-
Hmm. Looking at 2.1.8.3.2, it seems that unidirectional ManyToOnes are
legal. Maybe there's a bug in OpenJPA when putting a unidirectional
ManyToOne into a secondary table or something, or maybe it's just a
bug in all unidirectional ManyToOne cases.
-Patrick
On Nov 5, 2007 6:02 PM, Geir Magnusson
Exactly
But thanks all for the help.
geir
On Nov 5, 2007, at 8:37 PM, Patrick Linskey wrote:
I think he's actually trying to just have a single (unidirectional)
reference -- I think he added the backpointer just to see if he could
get things working that way.
-Patrick
On Nov 5, 2007 5:2
On Nov 5, 2007, at 8:22 PM, Patrick Linskey wrote:
I believe it's unidirectional ManyToOne (if that's legal). Each
InputFile is associated with one Show and one Show only, but multiple
InputFiles can be associated to the same Show.
I believe that what you're describing is a unidirectional on
I think he's actually trying to just have a single (unidirectional)
reference -- I think he added the backpointer just to see if he could
get things working that way.
-Patrick
On Nov 5, 2007 5:26 PM, Marina Vatkina <[EMAIL PROTECTED]> wrote:
> You need to have @OneToMany(mappedBy="show") - otherw
You need to have @OneToMany(mappedBy="show") - otherwise you get 2
unidirectional relationships, while you are trying to make them bidirectional.
Regards,
-marina
Geir Magnusson Jr. wrote:
To review, I have three tables :
Show, InputFile and a join table, Show2InputFile.
Show happens to be a
> I believe it's unidirectional ManyToOne (if that's legal). Each
> InputFile is associated with one Show and one Show only, but multiple
> InputFiles can be associated to the same Show.
I believe that what you're describing is a unidirectional one-to-one
with a join table. I think that you can m
To review, I have three tables :
Show, InputFile and a join table, Show2InputFile.
Show happens to be a subclass of InventoryItem using JOINED
inheritance strategy. Not sure if that matters. (I've seen some
weird behavior w/ Hibernate w/ JOINED, so I'm suspicious of it for no
rational re
That will be done after the voting is completed. There are also a list of
other tasks to be completed at that point in time.
http://openjpa.apache.org/releasing-openjpa.html - task " Thursday, 15:30"
Albert Lee.
On 11/5/07, Kevin Sutter <[EMAIL PROTECTED]> wrote:
>
> When do we update the docume
When do we update the documentation site? (
http://cwiki.apache.org/openjpa/documentation.html) Is that a post release
[vote] activity?
On 11/5/07, Albert Lee <[EMAIL PROTECTED]> wrote:
>
> I had another team member, who has access to the TCK license, ran the TCK
> before OPENJPA-370 is removed.
I had another team member, who has access to the TCK license, ran the TCK
before OPENJPA-370 is removed. I plan to do the same for this release
candidate.
If you can also give it a try, that would also be great. It does not hurt to
have another source to validate the image is good.
Thanks,
Albert
Albert-
Looks good to me. Were you able to run it against the TCK? If you
don't have access, I can run it here and make sure it passes.
On Nov 5, 2007, at 1:22 PM, Albert Lee wrote:
A candidate build for OpenJPA 1.0.1 maintenance release is available
at:
http://openjpa.apache.org/bui
A candidate build for OpenJPA 1.0.1 maintenance release is available at:
http://openjpa.apache.org/builds/1.0.1/downloads/
Please review these artifacts and signatures, and vote whether we should
release them as Apache OpenJPA version 1.0.1.
Release notes for this release are included in the
Where are the foreign keys?
Bear in mind that @OneToOne, @OneToMany, @ManyToMany, and @ManyToOne
are JPA annotations, not ER annotations. The concepts differ a bit.
-Patrick
On Nov 5, 2007 11:33 AM, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
>
> On Nov 5, 2007, at 2:07 PM, Patrick Linskey wro
Would like for OpenJPA to provide a platform for eclipse Dali
-
Key: OPENJPA-432
URL: https://issues.apache.org/jira/browse/OPENJPA-432
Project: OpenJPA
Issue Type: Wish
C
On Nov 5, 2007, at 2:07 PM, Patrick Linskey wrote:
What happens if you just use a @OneToOne instead of the @ManyToOne?
The problem is that it's not OneToOne
Can you describe this in more detail? (I.e., in terms of what your
schema looks like.)
Well, there's a Show table, w/ a pk, and the
> > What happens if you just use a @OneToOne instead of the @ManyToOne?
>
> The problem is that it's not OneToOne
Can you describe this in more detail? (I.e., in terms of what your
schema looks like.)
-Patrick
On Nov 5, 2007 10:40 AM, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
>
> On Nov 5, 2
On Nov 5, 2007, at 12:44 PM, Patrick Linskey wrote:
I'm a newbie, so I don't quite grok the question. Show itself
doesn't have any references to InputFile.
Aha! IIRC, @ManyToOne is only meaningful when used as the back side of
a @OneToMany.
We don't have that. There are reasons, and its i
> I'm a newbie, so I don't quite grok the question. Show itself
> doesn't have any references to InputFile.
Aha! IIRC, @ManyToOne is only meaningful when used as the back side of
a @OneToMany.
What happens if you just use a @OneToOne instead of the @ManyToOne?
-Patrick
On Nov 5, 2007 9:16 AM,
[
https://issues.apache.org/jira/browse/OPENJPA-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Linskey updated OPENJPA-428:
Attachment: OPENJPA-428-test.jar
Attached is a test case (source and compiled classes) tha
On Nov 5, 2007, at 11:48 AM, Patrick Linskey wrote:
Hi,
What does the other side of the relation look like?
I'm a newbie, so I don't quite grok the question. Show itself
doesn't have any references to InputFile.
Also, what does
the Show class look like?
in what way? Show is a subcla
Thanks a lot for replying,
I am going to have a look at these classes.
Julien.
2007/11/5, Patrick Linskey <[EMAIL PROTECTED]>:
>
> Hi,
>
> JPA annotations are parsed in the AnnotationPersistenceMetaDataParser
> and AnnotationPersistenceMappingParser. @Column is a JDBC-specific
> annotation, so is
Hi,
What does the other side of the relation look like? Also, what does
the Show class look like?
-Patrick
On Nov 5, 2007 8:08 AM, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
> I'm a newbie, so forgive me if I'm not asking the question the right
> way.
>
> I have a join table in my DB :
>
> +-
Hi,
JPA annotations are parsed in the AnnotationPersistenceMetaDataParser
and AnnotationPersistenceMappingParser. @Column is a JDBC-specific
annotation, so is handled by AnnotationPersistenceMappingParser.
Note that XML configuration files override the JPA annotations.
-Patrick
On Nov 5, 2007
I'm a newbie, so forgive me if I'm not asking the question the right
way.
I have a join table in my DB :
+-+--+--+-+-+---+
| Field | Type | Null | Key | Default | Extra |
+-+--+--+-+-+
Hello,
I am looking into the source code of OpenJpa and I am trying to better
understand how it is implemented.
My question relates to annotation processing by OpenJpa. Let's take a simple
JPA annotation : [EMAIL PROTECTED]/code].
I would like to know:
-What is the class in charge of processing t
[
https://issues.apache.org/jira/browse/OPENJPA-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540189
]
Richmond Stevenson commented on OPENJPA-294:
Try adding a path element to where ever your compiled class
35 matches
Mail list logo
