Bugzilla – Full Text Bug Listing
| Summary: | EclipseLink nosql does not recognize unique constrains with mongodb | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Jürgen Stadler <mail> |
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> |
| Status: | NEW --- | QA Contact: | |
| Severity: | critical | ||
| Priority: | P2 | CC: | jamesssss, jmcollin92, mail, tom.ware |
| Version: | unspecified | Keywords: | consistency, core, noteworthy |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| Whiteboard: | mongodb | ||
The mongo-db-driver used is version 2.10.0 Setting target and priority. See the following page for the meanings of these fields: http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines Community: Please vote for this bug if it is important to you. Votes are one of the main criteria we use to determine which bugs to fix next. Does Mongo throw an error for this constraint? If Mongo does not validate constraints, there is nothing EclipseLink can do. Check your log, are there any errors? Hi James,
> Check your log, are there any errors?
No, there is no error. The instruction is ignored. It may be a very insteresting feature to add if possible.
JM.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |
When adding a unique constraint like db.users.ensureIndex({username: 1}, {unique: true}) the entity manager just ignores this when persisting an entry with a conflicting username.