Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when deserializing document when object does not contains this property #32

Open
ti24horas opened this issue Sep 4, 2010 · 1 comment

Comments

@ti24horas
Copy link

When a field is added to the document and the object does not have this property, first, an OutOfmemoryException is thrown, then various errors occurs in other object deserialization that is not related with the first.
The workaround is remove the field from mongodb, then reset the pooled connections.
How to reproduce:

  1. Save an object with some properties;
  2. Retrieve the set of objects;
  3. Add some field using mongodb using $set: {SomeField: someValue}
  4. Retrieve the same set of objects. An error saying that the deserialization was failed because "SomeField" does not exist.
  5. Try to retrieve a set of objects from other collection. An OutOfMemoryException is thrown.
@thegrubbsian
Copy link

This is actually not specifically related to adding and removing fields. For me it appears to be a concurrency issue. There's a thread on the Google Group about this (http://groups.google.com/group/norm-mongodb/browse_thread/thread/af03b3eb1d016309)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants