this is likely
http://docs.sqlalchemy.org/en/rel_1_0/changelog/migration_10.html#the-insert-from-select-construct-now-implies-inline-true
- use explicit returning(). returned_defaults implies only a single row
INSERT which is not the case for INSERT from SELECT.
On 11/01/2015 01:29 AM, gbr
On 10/31/15 5:48 PM, r...@rosenfeld.to wrote:
> On Friday, October 30, 2015 at 6:02:47 PM UTC-5, r...@rosenfeld.to wrote:
>
> I would like to temporarily drop a foreign key constraint while
> loading data and then revert the constraint's removal when done.
> I'm hoping to do this
I've just tried to upgrade from 0.9.4 to the latest 1.0.9 version (yes, I'm
late) and am running into some problems. Most notably, `returned_defaults`
from an insert query does not seem to work as before. This is part of my
code:
new_record = select([user_id, parent_id, 1 +
New to python, web development and hence flask. I have a small application
that accepts excel inputs, extracts the data and writes it out oracle. My
stack includes flask-sqlalchemy, cx_oracle. When I upload a small excel
file with about 10 K rows, it works just fine. When I throw really large
On Friday, October 30, 2015 at 6:02:47 PM UTC-5, r...@rosenfeld.to wrote:
>
> I would like to temporarily drop a foreign key constraint while loading
> data and then revert the constraint's removal when done. I'm hoping to do
> this without needing any specific knowledge of the constraints
On 10/31/15 2:44 AM, Nana Okyere wrote:
> New to python, web development and hence flask. I have a small
> application that accepts excel inputs, extracts the data and writes it
> out oracle. My stack includes flask-sqlalchemy, cx_oracle. When I upload
> a small excel file with about 10 K rows,
