You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by "Andy Jefferson (JIRA)" <ji...@apache.org> on 2010/07/02 12:53:49 UTC

[jira] Created: (JDO-662) Extend "sequence" metadata to allow specification of start and allocationSize

Extend "sequence" metadata to allow specification of start and allocationSize
-----------------------------------------------------------------------------

                 Key: JDO-662
                 URL: https://issues.apache.org/jira/browse/JDO-662
             Project: JDO
          Issue Type: Improvement
          Components: api, specification, tck
            Reporter: Andy Jefferson
             Fix For: JDO 3 maintenance release 1


While the user can define to use a datastore sequence currently, with a particular name, they cannot define the allocation size and start point of that sequence to be used when creating it (if the implementation is creating it). Would make sense to allow these settings in the metadata

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


[jira] Commented: (JDO-662) Extend "sequence" metadata to allow specification of start and allocationSize

Posted by "Michael Bouschen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/JDO-662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923902#action_12923902 ] 

Michael Bouschen commented on JDO-662:
--------------------------------------

The patch JDO-662.patch looks good and I think it is ready to be checked in.



> Extend "sequence" metadata to allow specification of start and allocationSize
> -----------------------------------------------------------------------------
>
>                 Key: JDO-662
>                 URL: https://issues.apache.org/jira/browse/JDO-662
>             Project: JDO
>          Issue Type: Improvement
>          Components: api, specification, tck
>            Reporter: Andy Jefferson
>             Fix For: JDO 3 maintenance release 1
>
>         Attachments: JDO-662.patch
>
>
> While the user can define to use a datastore sequence currently, with a particular name, they cannot define the allocation size and start point of that sequence to be used when creating it (if the implementation is creating it). Would make sense to allow these settings in the metadata

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


[jira] Updated: (JDO-662) Extend "sequence" metadata to allow specification of start and allocationSize

Posted by "Andy Jefferson (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JDO-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy Jefferson updated JDO-662:
-------------------------------

    Attachment: JDO-662.patch

Updated patch with just the changes for this JIRA. Has updated XSD/DTD, updated @Sequence annotation, and updated javax.jdo.metadata.Sequence

> Extend "sequence" metadata to allow specification of start and allocationSize
> -----------------------------------------------------------------------------
>
>                 Key: JDO-662
>                 URL: https://issues.apache.org/jira/browse/JDO-662
>             Project: JDO
>          Issue Type: Improvement
>          Components: api, specification, tck
>            Reporter: Andy Jefferson
>             Fix For: JDO 3 maintenance release 1
>
>         Attachments: JDO-662.patch
>
>
> While the user can define to use a datastore sequence currently, with a particular name, they cannot define the allocation size and start point of that sequence to be used when creating it (if the implementation is creating it). Would make sense to allow these settings in the metadata

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


[jira] Updated: (JDO-662) Extend "sequence" metadata to allow specification of start and allocationSize

Posted by "Andy Jefferson (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JDO-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy Jefferson updated JDO-662:
-------------------------------

    Attachment: JDO-662.patch

Attached is a patch adding allocationSize and initialValue to the @Sequence annotation, and the equivalent to the DTD/XSD. Note that this patch also includes some other changes to the DTD/XSD required for JDO-660, whose validity should be checked as part of that JIRA

> Extend "sequence" metadata to allow specification of start and allocationSize
> -----------------------------------------------------------------------------
>
>                 Key: JDO-662
>                 URL: https://issues.apache.org/jira/browse/JDO-662
>             Project: JDO
>          Issue Type: Improvement
>          Components: api, specification, tck
>            Reporter: Andy Jefferson
>             Fix For: JDO 3 maintenance release 1
>
>         Attachments: JDO-662.patch
>
>
> While the user can define to use a datastore sequence currently, with a particular name, they cannot define the allocation size and start point of that sequence to be used when creating it (if the implementation is creating it). Would make sense to allow these settings in the metadata

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


[jira] Commented: (JDO-662) Extend "sequence" metadata to allow specification of start and allocationSize

Posted by "Craig L Russell (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/JDO-662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926339#action_12926339 ] 

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

Looks good.


> Extend "sequence" metadata to allow specification of start and allocationSize
> -----------------------------------------------------------------------------
>
>                 Key: JDO-662
>                 URL: https://issues.apache.org/jira/browse/JDO-662
>             Project: JDO
>          Issue Type: Improvement
>          Components: api, specification, tck
>            Reporter: Andy Jefferson
>             Fix For: JDO 3 maintenance release 1
>
>         Attachments: JDO-662.patch
>
>
> While the user can define to use a datastore sequence currently, with a particular name, they cannot define the allocation size and start point of that sequence to be used when creating it (if the implementation is creating it). Would make sense to allow these settings in the metadata

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


[jira] Updated: (JDO-662) Extend "sequence" metadata to allow specification of start and allocationSize

Posted by "Andy Jefferson (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JDO-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy Jefferson updated JDO-662:
-------------------------------

    Attachment:     (was: JDO-662.patch)

> Extend "sequence" metadata to allow specification of start and allocationSize
> -----------------------------------------------------------------------------
>
>                 Key: JDO-662
>                 URL: https://issues.apache.org/jira/browse/JDO-662
>             Project: JDO
>          Issue Type: Improvement
>          Components: api, specification, tck
>            Reporter: Andy Jefferson
>             Fix For: JDO 3 maintenance release 1
>
>         Attachments: JDO-662.patch
>
>
> While the user can define to use a datastore sequence currently, with a particular name, they cannot define the allocation size and start point of that sequence to be used when creating it (if the implementation is creating it). Would make sense to allow these settings in the metadata

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