[sqlalchemy] Re: Bizzarre insert behavior: NULL constraint violation with non-null value, column changes every run.

2015-07-28 Thread Bob Ternosky
Yes. In fact if I take the output parameterized SQL + values and combine them together and run vs SQL*Plus the insert works. Using this: 2015-07-28 11:12:40,844 INFO sqlalchemy.engine.base.Engine b'INSERT INTO corp.test_table (batch_id, batch_type, scheduled_date, status, emp_id, bill_per,

[sqlalchemy] Re: Bizzarre insert behavior: NULL constraint violation with non-null value, column changes every run.

2015-07-28 Thread Jonathan Vanasco
Have you tried toggling the sqlalchemy connection string? http://docs.sqlalchemy.org/en/rel_1_0/core/engines.html#sqlalchemy.create_engine.params.case_sensitive -- You received this message because you are subscribed to the Google Groups sqlalchemy group. To unsubscribe from this group and

[sqlalchemy] Re: Bizzarre insert behavior: NULL constraint violation with non-null value, column changes every run.

2015-07-28 Thread Bob Ternosky
I had not tested that parameter. But adding case_sensitive to my create_engine call with either =True or =False made no difference. On Tuesday, July 28, 2015 at 11:51:00 AM UTC-4, Jonathan Vanasco wrote: Have you tried toggling the sqlalchemy connection string?

[sqlalchemy] Re: Bizzarre insert behavior: NULL constraint violation with non-null value, column changes every run.

2015-07-28 Thread Jonathan Vanasco
Also, check this: http://docs.sqlalchemy.org/en/rel_1_0/dialects/oracle.html#identifier-casing -- You received this message because you are subscribed to the Google Groups sqlalchemy group. To unsubscribe from this group and stop receiving emails from it, send an email to

[sqlalchemy] Re: Bizzarre insert behavior: NULL constraint violation with non-null value, column changes every run.

2015-07-28 Thread Bob Ternosky
The actual create was done with all lowercase: CREATE TABLE test_table ( -batch_idNUMBER(10,0)NOT NULL, -batch_type NUMBER(2,0) NOT NULL, -scheduled_date DATENOT NULL, -