Apparently there is a gap in the spec around specifying the PK for a
join table, so this is a tricky case. We have to find some solution to
that.
Hi Michelle,
JPOX next nightly build (20050528) will only add/require this ADPT_PK_IDX
column if the Map/Set uses a non-PC key and where the
This sounds great, Andy! I'll try it out ASAP.
Thanks very much,
Michelle
Andy Jefferson wrote:
Apparently there is a gap in the spec around specifying the PK for a
join table, so this is a tricky case. We have to find some solution to
that.
Hi Michelle,
JPOX next nightly build
OK. You'll just have to put it down to not currently supported by JPOX
with that MetaData definition. We support M-N just in a different way.
Do you have an idea of when you might support this? The new metadata
tests I'm working on use the company model and this mapping, so I'm
wondering
Do you have an idea of when you might support this? The new metadata
tests I'm working on use the company model and this mapping, so I'm
wondering if I should bother to temporarily remap them for debugging.
sometime in the next month hopefully. Maybe sooner ...
You can just use the
I've done that, but then JPOX seems to want a primary key in the join
table and supplies it, though there is none in the schema or metadata.
[java] [FATAL] tck - Exception during setUp or runtest:
javax.jdo.JDODataStoreException: Put request failed : INSERT INTO
EMPLOYEE_PHONENO_TYPE
Hi Andy,
On May 26, 2005, at 8:35 AM, Andy Jefferson wrote:
What is this relationship causing the issue ? I'm guessing a Map in
Person of
String, String. It is a perfectly valid thing for an impl to want to
put a
PK on any table. It is also a valid thing for an impl to add
additional
Craig/Michelle,
Craig wrote:
In the company-derby.orm, the Project is mapped thus:
class name=Project table=projects
field name=projid column=PROJID primary-key=true/
field name=reviewers table=project_reviewer
join column=PROJID/
Below is a summary four test errors that are responsible for 90 out of a
total of 115 errors when running the tck on jpox/derby. The fourth one
listed is a test cleanup problem logged as JIRA JDO-48. Could the JPOX
team please take a look at the others?
Hi Andy,
In the company package.jdo, some of the information you need is there
class name=Employee
identity-type=application
field name=reviewedProjects
persistence-modifier=persistent
collection
Hi,
Below is a summary four test errors that are responsible for 90 out of a
total of 115 errors when running the tck on jpox/derby. The fourth one
listed is a test cleanup problem logged as JIRA JDO-48. Could the JPOX
team please take a look at the others?
14 tests fail with
10 matches
Mail list logo
