You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Background
MySQL treats booleans as either a 0 or 1. Our Batch connectors currently use schema inference which interprets data that takes the form of 0 or 1 as an integer.
This is suboptimal because ideally we would know that a boolean field was a boolean and correctly sync it to a destination.
Proposal
If a field only ever takes a value of 0 or 1, it would be ideal for schema inference to classify it as a boolean rather than an integer.
The text was updated successfully, but these errors were encountered:
Background
MySQL treats booleans as either a 0 or 1. Our Batch connectors currently use schema inference which interprets data that takes the form of 0 or 1 as an integer.
This is suboptimal because ideally we would know that a boolean field was a boolean and correctly sync it to a destination.
Proposal
If a field only ever takes a value of 0 or 1, it would be ideal for schema inference to classify it as a boolean rather than an integer.
The text was updated successfully, but these errors were encountered: