-
-
Notifications
You must be signed in to change notification settings - Fork 149
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
docs: thoroughly document DataTypes #11
Conversation
I'll fix the lint issue but feel free to review the contents :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What are the React files for?
Ah nevermind. Cool stuff |
Before merging I've noticed the two first datatype sections don't have links to the dialect documentations like the other ones. I should fix that. |
…te into ephys/new-datatypes-docs
Links to the different dbms documentations have been added IMO we can merge without @markdirish's review for db2/ibmi. We'll open a follow-up PR if necessary |
lgtm |
conflict fixed |
This PR rewrites the other-data-types page to thoroughly document every built-in DataType, and their corresponding SQL type (per dialect).
I based it on the DataTypes unit tests, as well as the documentation of the different dialects.
I'm unsure which documentation should be used for db2 & ibmi so there are likely errors in what I wrote for these 2 dialects. @markdirish if you have a minute to review this part, and/or point me to the right resources.
I've also documented common pain points, such as DataTypes.UUIDV4 being a JS function instead of a SQL one.
I've also moved the part about querying JSON to the page about Querying (with a link leading there), as that seems to be the place where people look for it.
I wrote a react component that filters out the columns of a table based on the user's preferred dialect :)