We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Consider the following SQL statement
CREATE TABLE foo( id int primary key, a varchar(255) null, b varchar(255) null default 'foo', c timestamp null default current_timestamp() );
Running this on vitess creates the table but the column c is not nullable. This is verified by running the following SQL statement
c
SELECT column_name column_name, data_type data_type, column_type full_data_type, column_default column_default, is_nullable is_nullable FROM information_schema.columns WHERE table_name = 'foo' ORDER BY ordinal_position;
Vitess results show that the column is not nullable but running the same queries on MySQL results in a nullable column
Steps to reproduce this issue, example:
The text was updated successfully, but these errors were encountered:
GuptaManan100
Successfully merging a pull request may close this issue.
Overview of the Issue
Consider the following SQL statement
Running this on vitess creates the table but the column
c
is not nullable. This is verified by running the following SQL statementVitess results show that the column is not nullable but running the same queries on MySQL results in a nullable column
Reproduction Steps
Steps to reproduce this issue, example:
The text was updated successfully, but these errors were encountered: