[hibernate-issues] [Hibernate-JIRA] Commented: (OGM-143) Implement dialect.nextValue in MongoDB

[Emmanuel Bernard (JIRA)]

    [ https://hibernate.onjira.com/browse/OGM-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46120#comment-46120 ] 

Emmanuel Bernard commented on OGM-143:
--------------------------------------

The sequence info is captured in the RowKey parameter passed to nextValue. A sequence is uniquely identified by the "table" hosting it as well as the segmentColumnName and segmentColumnValue. Check out OgmTableGenerator line 528 for the details

One question is should we have one document for all sequences in the same "table" or should it be one document per tuple table, segmentColumnName, segmentColumnValue? It seems one document per sequence will scale better as the comparison will be per sequence			and not encompass all sequences

> Implement dialect.nextValue in MongoDB
> --------------------------------------
>
>                 Key: OGM-143
>                 URL: https://hibernate.onjira.com/browse/OGM-143
>             Project: Hibernate OGM
>          Issue Type: New Feature
>          Components: datastore
>            Reporter: Emmanuel Bernard
>
> MongoDB ha the notion of findAndModify operation that is perfect to map nextValue.
> http://www.mongodb.org/display/DOCS/findAndModify+Command
> What they call side counter method http://www.mongodb.org/display/DOCS/How+to+Make+an+Auto+Incrementing+Field

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira