[
https://issues.apache.org/jira/browse/JDO-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509731
]
Craig Russell commented on JDO-403:
-----------------------------------
One point to clarify regarding table, catalog, schema.
With xml metadata, table, catalog, and schema appear together in the jdo,
package, class and interface elements. This allows the table to be defined
using an arbitrary schema and catalog.
But then, table appears without catalog and schema in property, field, join,
key, value, element, index, and unique. This would imply that the table
referenced by these elements must be in the same catalog and schema as the
corresponding class or interface in which they are embedded.
If catalog and schema are not specified, the table name itself is [[[database.]
catalog.] schema.] table.
Looking at annotations, we have @Table, @SecondaryTable, @JoinTable with
nothing in them save their name, catalog, and schema. I'm wondering what these
annotations are for?
> JDO2 Annotations
> ----------------
>
> Key: JDO-403
> URL: https://issues.apache.org/jira/browse/JDO-403
> Project: JDO
> Issue Type: New Feature
> Components: api2
> Affects Versions: JDO 2 final
> Reporter: Andy Jefferson
> Assignee: Michelle Caisse
> Fix For: JDO 2 maintenance release 1
>
> Attachments: embedded.patch, fkpk.patch, jdo_2_1_annotations.jar
>
>
> It would be desirable for JDO2 to have its own set of annotations. We have
> developed a set within JPOX that would likely serve as a starting point for
> such a set. In my opinion they should be
> 1. Split into javax.jdo.annotations.jdo and javax.jdo.annotations.orm
> 2. Move ORM attributes from some of the JDO annotations and have a ORM
> annotation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
