-
-
Notifications
You must be signed in to change notification settings - Fork 241
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
ORA-01790 on mass insert or update with version 6.0.x #558
Comments
Thanks for reporting, I was able to replicate the issue now. If you can, please do not hesitate to submit a PR for a Fix. |
Are you sure the issue only exists on 6.x? I think the problem is with the current implementation where batch insert uses -- Edit -- |
Thanks for finding the issue! Hopefully it will be easy to resolve. For now I have added a workaround in my own code so the error will not get triggered. This is okay for short term, but in the long run I would like to be able to use |
* 8.x: Bump v8.2.1 🚀 Add model insert tests. Add test for single insert. Fix binding values. Add failing tests for #558. Bump v8.2.0 🚀 Fix cs. Fix pagination tests. Enhance pagination as suggested on #563. Fix docs. Bump v8.1.3 🚀 Apply fixes from StyleCI Compare using actual db count. Use lower column name on column listing. Fix test suffix. Add failing tests for #596.
Fixed on v8.2.1 🚀 |
The problem
Whenever a mass insert is called (through a model or the query builder) oracle throws the following error:
The problem here is that I am trying to insert data into a table with a column that accepts either an integer or null.
For example:
I have a table with people. The job_id attribute can be null or an integer.
The
job_id
attribute on my Person in the first case isnull
.The
job_id
attribute on my Person in the second case issome id
.Due to not being the same data type the ORA-01790 exception is thrown, even if my
job_id
column can be either null or an integer.Example of code which results in an error:
Then:
OR
This has been occurring since updating to 6.0.x.
Version 5.8.x does not have this problem.
System details
The text was updated successfully, but these errors were encountered: