On 17.12.2014 20:37, Tony Locke wrote:
> On the question of extending the DB-API to accommodate prepared
> statements, from my narrow point of view as a maintainer of pg8000
> it's unnecessary, as pg8000 uses prepared statements for everything
> anyway. In later versions of Postgres, the query plan
On 17.12.2014 18:54, Michael Bayer wrote:
>
>> On Dec 17, 2014, at 10:41 AM, M.-A. Lemburg wrote:
>>
>>
>> Another possibility is to write a layer on top of the DB-API
>> to abstract the underlying queries away from the application
>> and only have the layer provide dedicated methods for the
>> t
> On Dec 17, 2014, at 10:41 AM, M.-A. Lemburg wrote:
>
>
> Another possibility is to write a layer on top of the DB-API
> to abstract the underlying queries away from the application
> and only have the layer provide dedicated methods for the
> things the application needs, such as query method
On 17.12.2014 16:18, SF Markus Elfring wrote:
>> Please explain what you want in more detail, so we can check
>> whether there's room for improvement :-)
>
> Can the SQL update statement be encapsulated by a dedicated Python
> class for example?
Sure. You could write a class that only supports up
On 17.12.2014 15:38, SF Markus Elfring wrote:
>>> Can the prepare() method return a handle for a SQL statement?
>>
>> The proposal says:
>>
>> """
>> Return values are not defined.
>> """
>
> How do you think about to change the application programming
> interface here?
>
> Would a class like "pr
On 17.12.2014 14:50, SF Markus Elfring wrote:
>> How about:
>>
>> """
>> The prepared operation is only available until the next call to
>> one of the .execute*() methods or another call to the .prepare()
>> method using a different command string than the one used for
>> preparing the previous ope
On 09.12.2014 13:24, Daniele Varrazzo wrote:
> On Tue, Dec 9, 2014 at 9:40 AM, M.-A. Lemburg wrote:
>> On 07.12.2014 22:06, SF Markus Elfring wrote:
>>> Hello,
>>>
>>> An interface for parameterised SQL statements (working with
>>> placeholders) is provided by the execute() method from the Cursor
