On 10/19/15 3:39 PM, m1yag1 wrote:
> I have the following in my upgrade function of the revision file:
>
> |
> |
>
> defupgrade():
> op.add_column('gates_experiment_users',
> sa.Column('experiment_group',
> postgresql.ENUM('Control',
>
I have the following in my upgrade function of the revision file:
def upgrade():
op.add_column('gates_experiment_users',
sa.Column('experiment_group',
postgresql.ENUM('Control',
'SPARFA-50',
On 10/19/15 11:57 AM, Mike Bayer wrote:
>
>
> On 10/19/15 11:44 AM, Steven Winfield wrote:
>> The problem seems to be that the result set from an executemany() call
>> in psycopg2 is discarded - here is a good stackoverflow article on this
>> subject:
>> http://stackoverflow.com/questions/21624
On 10/19/15 11:44 AM, Steven Winfield wrote:
> The problem seems to be that the result set from an executemany() call
> in psycopg2 is discarded - here is a good stackoverflow article on this
> subject:
> http://stackoverflow.com/questions/21624844/getting-ids-of-multiple-rows-inserted-in-psycopg
The problem seems to be that the result set from an executemany() call in
psycopg2 is discarded - here is a good stackoverflow article on this
subject:
http://stackoverflow.com/questions/21624844/getting-ids-of-multiple-rows-inserted-in-psycopg2
In _emit_update_statements in orm/persistence.py,
Hi,
We are currently trying to upgrade to sqlalchemy 1.0.8 and have hit a
problem with executemany() and row versioning. We are using postgres and
psycopg2 as a backend. We have tables that use server side versioning (as
discussed at
http://docs.sqlalchemy.org/en/rel_0_9/orm/versioning.html#se
