Duplicate key error when using change tracking. #649
Assignees
Labels
Comments
|
Switching models to the memory connector does not cause this problem. Any ideas why this is happening? |
|
@ritch you know most about the replication algo, could you please investigate? |
|
see pull request. #668 |
|
Fixed by #668. A new version will be released in next few days. |
raymondfeng
pushed a commit
that referenced
this issue
Nov 19, 2014
2.8.0 * Expose more loopback middleware for require (Raymond Feng) * Scope app middleware to a list of paths (Miroslav Bajtoš) * Update CONTRIBUTING.md (Alex Voitau) * Fix the model name for hasMany/through relation (Raymond Feng) * Fixing the model attach (wfgomes) * Minor: update jsdoc for PersistedModel.updateAll (Alex Voitau) * AccessToken: optional `options` in findForRequest (Miroslav Bajtoš) * server-app: improve jsdoc comments (Miroslav Bajtoš) * server-app: middleware API improvements (Miroslav Bajtoš) * typo of port server (wfgomes) * Move middleware sources to `server/middleware` (Miroslav Bajtoš) * app.middleware: verify serial exec of handlers (Miroslav Bajtoš) * Simplify `app.defineMiddlewarePhases` (Miroslav Bajtoš) * Make sure loopback has all properties from express (Raymond Feng) * Implement `app.defineMiddlewarePhases` (Miroslav Bajtoš) * Implement app.middlewareFromConfig (Miroslav Bajtoš) * middleware/token: store the token in current ctx (Miroslav Bajtoš) * Fix `loopback.getCurrentContext` (Miroslav Bajtoš) * Update chai to ^1.10.0 (Miroslav Bajtoš) * package: fix deps (Miroslav Bajtoš) * Middleware phases - initial implementation (Miroslav Bajtoš) * Allows ACLs/settings in model config (Raymond Feng) * Remove context middleware per Ritchie (Rand McKinney) * Add API doc for context middleware - see #337 (crandmck) * Update persisted-model.js (Rand McKinney) * rest middleware: clean up context config (Miroslav Bajtoš) * Move `context` example to a standalone app (Miroslav Bajtoš) * Enable the context middleware from loopback.rest (Raymond Feng) * Add context propagation middleware (Raymond Feng) * Changes to JSdoc comments (Rand McKinney) * Reorder classes alphabetically in each section (Rand McKinney) * common: coding style cleanup (Miroslav Bajtoš) * Coding style cleanup (Gruntfile, lib) (Miroslav Bajtoš) * Enable jscs for `lib`, fix style violations (Rob Halff) * Add access-context.js to API doc (Rand McKinney) * Remove doc for debug function (Rand McKinney) * Update registry.js (Rand McKinney) * Fix the jsdoc for User.login (Raymond Feng) * Deleted instantiation of new Change model. This PR removes the instantiation of a new change model as models return from Change.find are already instances of Change. This solves the duplicate Id issue #649 (Berkeley Martinez) * Expose path to the built-in favicon file (Miroslav Bajtoš) * Add API docs for `loopback.static`. (Miroslav Bajtoš) * Add test for `remoting.rest.supportedTypes` (Miroslav Bajtoš) * Revert "rest handler options" (Miroslav Bajtoš) * REST handler options. (Guilherme Cirne) * The elapsed time in milliseconds can be 0 (less than 1 ms) (Raymond Feng)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using loopback 2.4.1
When using change tracking and creating a new instance of a model. A new model is created and a change model instance is also created, then the server crashes with the following.
This duplicate key problem also occurs when using the postgresql connector.
I created a repo that replicates the issue here.
The text was updated successfully, but these errors were encountered: