-
Notifications
You must be signed in to change notification settings - Fork 1
Add support for non-null ReferencedField optimization using model info #104
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
base: master
Are you sure you want to change the base?
Conversation
802dd63 to
50dced9
Compare
|
@balena-ci retest |
305f95c to
8c28cf9
Compare
79e5a63 to
5503416
Compare
| test.rule( | ||
| 'It is necessary that each plane that at least 3 pilots can fly, has a name', | ||
| `\ | ||
| SELECT 1 AS "result";`, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is what it looks like when you write a rule that cannot be broken :P
| Term: nickname | ||
| Concept Type: Short Text (Type) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I needed a nullable term to actually be able to test we generated sensible rules as opposed to having them all optimized away to nothing because they couldn't be broken :|
6a74c34 to
c290a56
Compare
c290a56 to
75c6d33
Compare
|
@balena-ci retest |
75c6d33 to
d61d299
Compare
We automatically use the model info to optimize rules/check constraints when compiling the schema. Change-type: minor
d61d299 to
37f50ae
Compare
We automatically use the model info to optimize rules/check constraints
when compiling the schema.
Change-type: minor