Re: speed concerns with executemany()

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: mike bayer <mike_mp(at)zzzcomputing(dot)com>, psycopg(at)postgresql(dot)org
Subject: Re: speed concerns with executemany()
Date: 2017-01-09 16:45:45
Message-ID: f71520d9-fecc-5e5f-a25a-8149e5a2e502@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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)

In response to

Responses

Browse psycopg by date

  From Date Subject
Next Message mike bayer 2017-01-09 23:12:12 Re: speed concerns with executemany()
Previous Message mike bayer 2017-01-09 16:04:32 Re: speed concerns with executemany()