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

complex field #924

Closed
wants to merge 2 commits into from
Closed

complex field #924

wants to merge 2 commits into from

Conversation

Catstyle
Copy link
Contributor

@Catstyle Catstyle commented Apr 1, 2015

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)

Review on Reviewable

@landscape-bot
Copy link

Code Health
Repository health increased by 0.11% when pulling 5573080 on Catstyle:feature/complex_field_issue into cbd2a44 on MongoEngine:master.

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 5573080 on Catstyle:feature/complex_field_issue into * on MongoEngine:master*.

@landscape-bot
Copy link

Code Health
Repository health increased by 0.11% when pulling fd4ae6a on Catstyle:feature/complex_field_issue into cbd2a44 on MongoEngine:master.

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling fd4ae6a on Catstyle:feature/complex_field_issue into * on MongoEngine:master*.

7 similar comments
@coveralls
Copy link

Coverage Status

Changes Unknown when pulling fd4ae6a on Catstyle:feature/complex_field_issue into * on MongoEngine:master*.

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling fd4ae6a on Catstyle:feature/complex_field_issue into * on MongoEngine:master*.

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling fd4ae6a on Catstyle:feature/complex_field_issue into * on MongoEngine:master*.

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling fd4ae6a on Catstyle:feature/complex_field_issue into * on MongoEngine:master*.

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling fd4ae6a on Catstyle:feature/complex_field_issue into * on MongoEngine:master*.

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling fd4ae6a on Catstyle:feature/complex_field_issue into * on MongoEngine:master*.

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling fd4ae6a on Catstyle:feature/complex_field_issue into * on MongoEngine:master*.

@MRigal
Copy link
Member

MRigal commented Apr 3, 2015

Please add one or two test cases here. I think you could build one quite easily out of the issue

@landscape-bot
Copy link

Code Health
Repository health decreased by 0.26% when pulling fd4ae6a on Catstyle:feature/complex_field_issue into 7f442f7 on MongoEngine:master.

@bagerard
Copy link
Collaborator

bagerard commented Jan 1, 2023

Closing as very old and unclear what the problem is or if it still exist (no test case)

@bagerard bagerard closed this Jan 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants