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

Resolve inconsistency between VARCHAR and STRING #1044

Closed
ybyzek opened this issue Feb 2, 2022 · 0 comments · Fixed by #1063
Closed

Resolve inconsistency between VARCHAR and STRING #1044

ybyzek opened this issue Feb 2, 2022 · 0 comments · Fixed by #1063
Assignees

Comments

@ybyzek
Copy link
Contributor

ybyzek commented Feb 2, 2022

Porting confluentinc/ksqldb-recipes#146 here

confluentinc/ksqldb-recipes#131 (comment)

Looking for clarification on differentiation of VARCHAR vs STRING and when to use which. I usually see VARCHAR in the context below, but STRING also works:

CREATE STREAM pages (
   page STRING, ....

We have recipes that reference both...

ksqlDB uses STRING as synonym to VARCHAR -- so semantically there is no difference.

VARCHAR is the standard SQL type, even if it actually needs a "max size" parameter that ksqlDB does not implement. -- STRING is no standard SQL type (seems to be syntactic sugar -- but sure why ksqlDB added it). To technically neither VARCHAR nor STRING is standard SQL...

To avoid confusing users, it might be good to just pick either one and use it exclusively in all tutorials.

Vote from @mjsax is to use VARCHAR

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 a pull request may close this issue.

1 participant