Re: [psycopg] speed concerns with executemany() - Mailing list psycopg

From Jim Nasby
Subject Re: [psycopg] speed concerns with executemany()
Date
Msg-id f71520d9-fecc-5e5f-a25a-8149e5a2e502@BlueTreble.com
Whole thread Raw
In response to Re: [psycopg] speed concerns with executemany()  (mike bayer <mike_mp@zzzcomputing.com>)
Responses Re: [psycopg] speed concerns with executemany()  (mike bayer <mike_mp@zzzcomputing.com>)
List psycopg
On 1/9/17 10:04 AM, mike bayer wrote:
> SQLAlchemy can definitely ignore the aggregated rowcount as most DBAPIs
> don't support it anyway, so we can flip the flag off if we know exactly
> what psycopg version breaks it.

ISTM it'd be better to add an attribute to indicate whether rowcount was
available or not, especially since it would be available with a page
size of 1?
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)


psycopg by date:

Previous
From: mike bayer
Date:
Subject: Re: [psycopg] speed concerns with executemany()
Next
From: mike bayer
Date:
Subject: Re: [psycopg] speed concerns with executemany()