Re: Solving the SQL composition problem

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
Cc: Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com>, "psycopg(at)postgresql(dot)org" <psycopg(at)postgresql(dot)org>
Subject: Re: Solving the SQL composition problem
Date: 2017-01-03 16:35:50
Message-ID: 0A40E4F5-C5D4-480D-BD90-40BC1253278C@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: psycopg


> On Jan 3, 2017, at 08:24, Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> wrote:
> What I'm suggesting is to let Postgres handle the replacement of normal values, using the prepared statement syntax of $1, $2, etc[1], and only do identifier replacement in python (using quote_ident).

If this is practical, I'd be very much in favor of it, for the reasons given.

--
-- Christophe Pettus
xof(at)thebuild(dot)com

In response to

Browse psycopg by date

  From Date Subject
Next Message Daniele Varrazzo 2017-01-03 16:40:57 Re: Solving the SQL composition problem
Previous Message Daniele Varrazzo 2017-01-03 16:33:56 Re: Solving the SQL composition problem