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
complex field #924
complex field #924
Conversation
…micField to subclass from ComplexField
|
Changes Unknown when pulling 5573080 on Catstyle:feature/complex_field_issue into * on MongoEngine:master*. |
|
Changes Unknown when pulling fd4ae6a on Catstyle:feature/complex_field_issue into * on MongoEngine:master*. |
7 similar comments
Changes Unknown when pulling fd4ae6a on Catstyle:feature/complex_field_issue into * on MongoEngine:master*. |
Changes Unknown when pulling fd4ae6a on Catstyle:feature/complex_field_issue into * on MongoEngine:master*. |
Changes Unknown when pulling fd4ae6a on Catstyle:feature/complex_field_issue into * on MongoEngine:master*. |
Changes Unknown when pulling fd4ae6a on Catstyle:feature/complex_field_issue into * on MongoEngine:master*. |
Changes Unknown when pulling fd4ae6a on Catstyle:feature/complex_field_issue into * on MongoEngine:master*. |
Changes Unknown when pulling fd4ae6a on Catstyle:feature/complex_field_issue into * on MongoEngine:master*. |
Changes Unknown when pulling fd4ae6a on Catstyle:feature/complex_field_issue into * on MongoEngine:master*. |
Please add one or two test cases here. I think you could build one quite easily out of the issue |
|
Closing as very old and unclear what the problem is or if it still exist (no test case) |
1 do not mark complex field as changed when parse from son
2 change DynamicField to subclass from ComplexField
1: since no data actually store in db, then no need to append it to changed_fields, otherwise when call save method without changes, they will appear in removals set unnecessarily
2: as metioned: #889 (comment)