-
Notifications
You must be signed in to change notification settings - Fork 707
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
"NULL in non-nullable column" error should include the offending table and column name #1268
Labels
Comments
vlsi
added a commit
to vlsi/Exposed
that referenced
this issue
Jun 19, 2021
* Exception message would include the relevant table and column name * LiteralOp(...) and QueryParameter(...) would fail if user creates NULL value for non-nullable type * Single-value QueryBuilder#registerArgument is slightly faster as it no longer creates list fixes JetBrains#1268
vlsi
added a commit
to vlsi/Exposed
that referenced
this issue
Jun 19, 2021
* Exception message would include the relevant table and column name * LiteralOp(...) and QueryParameter(...) would fail if user creates NULL value for non-nullable type * Single-value QueryBuilder#registerArgument is slightly faster as it no longer creates list fixes JetBrains#1268
vlsi
added a commit
to vlsi/Exposed
that referenced
this issue
Jun 19, 2021
* Exception message would include the relevant table and column name * LiteralOp(...) and QueryParameter(...) would fail if user creates NULL value for non-nullable type * Single-value QueryBuilder#registerArgument is slightly faster as it no longer creates list fixes JetBrains#1268
vlsi
added a commit
to vlsi/Exposed
that referenced
this issue
Jun 19, 2021
* Exception message would include the relevant table and column name * LiteralOp(...) and QueryParameter(...) would fail if user creates NULL value for non-nullable type * Single-value QueryBuilder#registerArgument is slightly faster as it no longer creates list fixes JetBrains#1268
vlsi
added a commit
to vlsi/Exposed
that referenced
this issue
Jun 19, 2021
* Exception message would include the relevant table and column name * LiteralOp(...) and QueryParameter(...) would fail if user creates NULL value for non-nullable type * Single-value QueryBuilder#registerArgument is slightly faster as it no longer creates list fixes JetBrains#1268
vlsi
added a commit
to vlsi/Exposed
that referenced
this issue
Jun 19, 2021
* Exception message would include the relevant table and column name * LiteralOp(...) and QueryParameter(...) would fail if user creates NULL value for non-nullable type * Single-value QueryBuilder#registerArgument is slightly faster as it no longer creates list fixes JetBrains#1268
vlsi
added a commit
to vlsi/Exposed
that referenced
this issue
Jun 19, 2021
* Exception message would include the relevant table and column name * LiteralOp(...) and QueryParameter(...) would fail if user creates NULL value for non-nullable type * Single-value QueryBuilder#registerArgument is slightly faster as it no longer creates list fixes JetBrains#1268
vlsi
added a commit
to vlsi/Exposed
that referenced
this issue
Jun 19, 2021
* Exception message would include the relevant table and column name * LiteralOp(...) and QueryParameter(...) would fail if user creates NULL value for non-nullable type * Single-value QueryBuilder#registerArgument is slightly faster as it no longer creates list fixes JetBrains#1268
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
exposed-core:0.31.1
Please add the relevant context information so users could tell what was wrong with the code.
In my case, the error was caused by
val refId = reference(...)
instead ofval refId = optReference(...)
.The actual DB model was "optional foreign key", so the proper API should be
optReference
.However, the strange thing is
reference(..)
field accepts nulls, andoptReference(..)
rejects null inupdate
andinsert
.The text was updated successfully, but these errors were encountered: