-
Notifications
You must be signed in to change notification settings - Fork 126
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
Support indexes, add Index and Unique annotation #123
Conversation
…roperty) The tests keep exploding with this though: ObjectBoxException: failed to create store: 10501 No index ID/UID assigned for indexed property: Property uByte (15, Byte) Even objectbox-model.json seems normal.
…ing apart @unique and @Index are sharing the same logic.
After turning them off this popped beautiful gem up: ObjectBoxException: failed to create store: 10001 State condition failed in assignIdsForProperty:476: indexId <= catalog.lastIndexId()
Unrequested review: I think my |
@Buggaboo Yeah, thanks. This is not done, yet. Hence the draft status. |
# Conflicts: # generator/lib/src/entity_resolver.dart # lib/src/annotations.dart # lib/src/bindings/bindings.dart # lib/src/bindings/signatures.dart # lib/src/modelinfo/modelentity.dart # lib/src/modelinfo/modelproperty.dart # lib/src/util.dart # test/entity.dart
116069a
to
7577849
Compare
7577849
to
859ba5d
Compare
Fixed issues, added tests and cleaned up. fast-tracking this to get on with other PRs but please have a look at the changes @greenrobot-team |
@vaind Invalid usages of the annotations and index type are not tested, otherwise LGTM. Thanks for finishing this! (You even caught all TODOs and left-over code removals!) |
Continuation of #120
Making progress.
Overall I'm not sure if there should be separate annotations vs. using flags on the existing
@Property
annotation.