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

Type system #1965

Open
aljazerzen opened this issue Feb 26, 2023 · 0 comments
Open

Type system #1965

aljazerzen opened this issue Feb 26, 2023 · 0 comments
Labels
language-design Changes to PRQL-the-language major-feature

Comments

@aljazerzen
Copy link
Member

Up until now, PRQL hasn't defined what "relation" is, at least on the language
level. We've been talking about numbers, arithmetic operations and datetimes,
without really defining them and offloading their definitions to what ever
database each of us has in mind. But their definitions are important, with
the simplest example of expression 4 - 5, which has different results depending
on whether integers are signed or not.

So goal of this issue is to settle the definition of what our functions are
operating on. This will allow us to define what results of expressions should
be
and then try to implement that behavior for each of the DBMSs.

This will obviously (and hopefully) trigger lots of responses.
To structure the discussion better, I've written something resembling a RFC in PR #1964.
I suggest we use review comments to stay on topic.

This issue can remain open as a tracking issue for new type-system-related issues
and for PRs implementing it.

Ref #381

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
language-design Changes to PRQL-the-language major-feature
Projects
None yet
Development

No branches or pull requests

1 participant