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

Decide on modeling of different numeric semantics in test suite #39

Open
alancai98 opened this issue Oct 6, 2022 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@alancai98
Copy link
Member

Across different SQL-compliant databases, there are different semantics related to some numeric operations, including:

  • integer overflow/underflow
  • rounding
  • division by 0
  • (some other cases)

The SQL-92 spec doesn't make the above cases clear. Some databases will error in the above cases, while others may return NULL or saturate to some default value. The PartiQL spec does not formalize this behavior as it may be operation and implementation-dependent. The conformance test suite should provide some way to configure the runtime numeric semantics for the above cases (e.g. through a test struct option or some namespace).

DoD

  • Define all the numeric operation semantics that are definable in the test suite
  • Create set of tests for each of the different numeric operation semantics
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant