-
Notifications
You must be signed in to change notification settings - Fork 403
When using JSONB with BlobColumn nullable, it doesn't accept null #3441
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
Comments
I will take a look at this example, but the best way to apply type converters to nullable columns is to just make the converter non-nullable, e.g.
If drift encounters such a type converter on a nullable column, it will implicitly add the |
I've tried to use it like that, but it still gives me an error:
The only way drift generates this:
is using it like this:
or else it never generates the "asNullable" part. But then it goes back to the error in the generated file |
Sorry, I didn't see that you tried the intended way in the issue description already. That problem should be fixed with 00e65cb. The reason the first approach doesn't work is essentially a variance issue. |
Uh oh!
There was an error while loading. Please reload this page.
I'm using the new JSONB column, but I want it to be nullable, and it seems that the converter doesn't accept "null"
Also, I'm using the develop branch files which contain the fix #3436
Even if I try exactly like the documentation using:
I get this error in the drift generated file:
The text was updated successfully, but these errors were encountered: