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

Add support for non-null ReferencedField optimization using model info #104

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Page-
Copy link
Contributor

@Page- Page- commented Jan 1, 2021

We automatically use the model info to optimize rules/check constraints
when compiling the schema.

Change-type: minor

@Page-
Copy link
Contributor Author

Page- commented Jan 1, 2021

@balena-ci retest

@Page- Page- marked this pull request as ready for review January 1, 2021 15:16
@Page- Page- requested a review from a team as a code owner January 1, 2021 15:16
@Page- Page- force-pushed the model-based-optimizations branch 2 times, most recently from 305f95c to 8c28cf9 Compare January 1, 2021 16:35
@Page- Page- marked this pull request as draft January 1, 2021 17:11
@Page- Page- force-pushed the model-based-optimizations branch 2 times, most recently from 79e5a63 to 5503416 Compare January 1, 2021 17:20
@@ -215,6 +223,12 @@ SELECT NOT EXISTS (
test.rule(
'It is necessary that each plane that at least 3 pilots can fly, has a name',
`\
SELECT 1 AS "result";`,
Copy link
Contributor Author

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

Comment on lines +29 to +30
Term: nickname
Concept Type: Short Text (Type)
Copy link
Contributor Author

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 :|

@Page- Page- force-pushed the model-based-optimizations branch 3 times, most recently from 6a74c34 to c290a56 Compare January 1, 2021 20:31
@Page- Page- changed the title Add the ability to optimize generated sql using model info Add support for non-null ReferencedField optimization using model info Jan 1, 2021
@Page- Page- marked this pull request as ready for review January 1, 2021 22:29
@Page-
Copy link
Contributor Author

Page- commented Jan 1, 2021

@balena-ci retest

@Page- Page- marked this pull request as draft January 1, 2021 22:30
We automatically use the model info to optimize rules/check constraints
when compiling the schema.

Change-type: minor
@Page- Page- force-pushed the model-based-optimizations branch from d61d299 to 37f50ae Compare May 3, 2021 10:46
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

Successfully merging this pull request may close these issues.

1 participant