Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jdo-dev@db.apache.org
Message-ID: <6683062.499591285950813288.JavaMail.jira@thor>
Date: Fri, 1 Oct 2010 12:33:33 -0400 (EDT)
From: "Craig L Russell (JIRA)" <jira@apache.org>
To: jdo-dev@db.apache.org
Subject: [jira] Commented: (JDO-660) Ability to specify positioning of field
 'column(s)' in datastore "table"
In-Reply-To: <7644923.18201276151773806.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/JDO-660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916940#action_12916940 ] 

Craig L Russell commented on JDO-660:
-------------------------------------

With regard to the patch, perhaps we should just create the 3.1 dtd and xsd files separately and then provide changes in this patch.


> Ability to specify positioning of field 'column(s)' in datastore "table"
> ------------------------------------------------------------------------
>
>                 Key: JDO-660
>                 URL: https://issues.apache.org/jira/browse/JDO-660
>             Project: JDO
>          Issue Type: New Feature
>          Components: api, specification, tck
>            Reporter: Andy Jefferson
>             Fix For: JDO 3 maintenance release 1
>
>         Attachments: JDO-660.patch
>
>
> With an RDBMS datastore, when generating the schema, it is desirable to be able to specify the positioning of the column(s) of a field in the generated table. 
> With spreadsheet documents, it is critical to be able to define which column number is used for a particular field.
> With other datastores it is also likely desirable.
> To achieve this I propose adding an attribute to the XML <column> called "position". Similarly for the @Column annotation.
> This can take integer values with 0-origin.
> Complications : 
> 1. how this is handled when we have inheritance. If a root class has subclass-table inheritance, then those fields are persisted into the tables of all subclasses, and we may want to override the positions for those individually - to that end the user can override the metadata of the superclass fields. 
> 2. anything else ?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.