From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | matshyeq <matshyeq(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: libpq - lack of support to set the fetch size |
Date: | 2014-03-12 13:53:58 |
Message-ID: | 532066F6.3000402@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 03/12/2014 06:05 AM, matshyeq wrote:
> Don't fully agree with last statement. FETCH is WAY better and more
> functional than LIMIT.
>
> PQsetSingleRowMode() is not meant for partial resultsets, but it can
> be used if you accept the downsides.
>
> Given the 'discretion mode' I'm still not sure if that's a proper and
> elegant way to meet the requirement.
Following this discussion it would seem that Postgres meets the
requirement, but that what you want is that the interfaces you use make
use of the capabilities. As mentioned previously the JDBC driver and the
Python driver(psycopg2) already do what you want. The next step, to me
at least, is take what you have learned and contact the projects
(DBD::Pg, pgAdmin) in question.
> Maybe it is? Anyway, This is just me, an end user giving you, the
> PostgreSQL maintaining developers a chance to hear 'the voice of the
> customer'
>
> Regards,
> ~Msciwoj
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | bobJobS | 2014-03-12 15:19:50 | High Level Committers Wanted |
Previous Message | Ian Lawrence Barwick | 2014-03-12 13:28:03 | Re: Materialized view from PG to Oracle? |