Repository navigation
(BREAKING: 0.5) patch nullable inference in Postgres using EXPLAIN - #566
Merged
Merged
Conversation
abonander
force-pushed
the
ab/postgres-nullable
branch
from
July 27, 2020 08:30
38f79e0 to
ea0c1a9
Compare
abonander
force-pushed
the
ab/postgres-nullable
branch
from
July 27, 2020 08:43
ea0c1a9 to
9f5dd8f
Compare
abonander
force-pushed
the
ab/postgres-nullable
branch
from
July 27, 2020 08:59
9f5dd8f to
67d6cb4
Compare
abonander
force-pushed
the
ab/postgres-nullable
branch
3 times, most recently
from
July 27, 2020 09:17
bd750bb to
ffba4b6
Compare
abonander
force-pushed
the
ab/postgres-nullable
branch
from
July 27, 2020 20:01
ffba4b6 to
9ef7d1b
Compare
BREAKING CHANGE: some columns in `query!()` et. al. output will change from `T` to `Option<T>` breakage should be minimal in practice as these columns will need to have been manually overridden anyway to avoid runtime errors Signed-off-by: Austin Bonander <austin@launchbadge.com>
abonander
force-pushed
the
ab/postgres-nullable
branch
from
July 27, 2020 20:03
9ef7d1b to
711a24c
Compare
abonander
marked this pull request as ready for review
July 27, 2020 20:03
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
BREAKING CHANGE: some columns emitted by
query!()andquery_as!(), primarily those brought in by a[LEFT | RIGHT | FULL] JOINwill becomeOption<T>where they wereTbefore.In practice breakage should be minimal as these would result in
UnexpectedNullerrors at runtime unless they were manually overridden withfoo as "foo?"already.However, I expect there to be edge cases that aren't covered yet, thus why we've chosen to land this in 0.5 and kick out an early alpha for testing.
jsonfeature (and thus theserdeandserde_jsonfeatures) to always be on forpostgres(to parseEXPLAIN VERBOSEoutput, possible formats are JSON, XML, YAML or text)closes #367