[hibernate-issues] [Hibernate-JIRA] (OGM-156) Avoid using a table scan with MongoDB nextValue implementation

Emmanuel Bernard (JIRA) noreply at atlassian.com
Thu Sep 27 05:00:37 EDT 2012

Previous message: [hibernate-issues] [Hibernate-JIRA] (OGM-180) Make MongoDB safe option defaults true in Hibernate OGM
Next message: [hibernate-issues] [Hibernate-JIRA] (OGM-179) Consider whether or not it is fine to store the same id value in both the identifier column and _id in MongoDB
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hibernate-issues/attachments/20120927/7d8b6de5/attachment-0001.html

Previous message: [hibernate-issues] [Hibernate-JIRA] (OGM-180) Make MongoDB safe option defaults true in Hibernate OGM
Next message: [hibernate-issues] [Hibernate-JIRA] (OGM-179) Consider whether or not it is fine to store the same id value in both the identifier column and _id in MongoDB
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the hibernate-issues mailing list