On 12/03/21, Daniele Varrazzo (daniele.varra...@gmail.com) wrote:
> I have just merged the connection pool branch to main in psycopg3. I
> am very happy about this object and I think it's an immense
> improvement compared to psycopg2 pool. The documentation is already
> online:
>
> - behaviour des
On 08/02/21, Adrian Klaver (adrian.kla...@aklaver.com) wrote:
> On 2/8/21 4:16 AM, Daniele Varrazzo wrote:
> > 1) We can provide a feature to select the type of cursor that is not
> > much dissimilar from psycopg2
> > 2) Do we need DictCursor/RealDictCursor? ISTM that one of the two
> > would be s
On 08/02/21, Daniele Varrazzo (daniele.varra...@gmail.com) wrote:
> > - There appears to be no card about dictcursor on the project board.
> > What's the plan (and priority) for that (if any)?
...
> In psycopg2 there are:
>
> - DictCursor (returns a hybrid object between a sequence and a diction
On 02/12/20, Daniele Varrazzo (daniele.varra...@gmail.com) wrote:
> I'm toying with the idea of adding a 'connection.execute(query,
> [params])' methd, which would basically just create a cursor
> internally, query on it, and return it. No parameter could be passed
> to the cursor() call, so it cou
On 10/11/20, Daniele Varrazzo (daniele.varra...@gmail.com) wrote:
> On Tue, 10 Nov 2020 at 03:22, Christophe Pettus wrote:
> >
> > > On Nov 9, 2020, at 19:20, Daniele Varrazzo
> > > wrote:
> > >
> > >Choices to cast Python ``int`` type:
> >
> > Is it absurd to make the choice at execution ti
On 10/11/20, Daniele Varrazzo (daniele.varra...@gmail.com) wrote:
> Anyone against using "psycopg" as package name, and starting from 3 as
> version number?
Personally I think the "3" in "psycopg3" is clearer than simply
"psycopg" in relation to this being an evolution of the psycopg2
package.
Ro
On 26/05/20, Frank Millman (fr...@chagford.com) wrote:
>
>
> On 2020-05-26 3:08 PM, Rory Campbell-Lange wrote:
> > On 26/05/20, Frank Millman (fr...@chagford.com) wrote:
> > Does using %s instead of {}.format help solve the issue?
>
> To reproduce my situation, you s
On 26/05/20, Frank Millman (fr...@chagford.com) wrote:
> On 2020-05-26 2:11 PM, Daniele Varrazzo wrote:
> > No, we don't want to add any intelligence in trying to figure out what
> > is into a query. If you are comfortable that you will be using always
> > the same pattern for comments you can easi
On 26/05/20, Frank Millman (fr...@chagford.com) wrote:
> I have a function that returns a complex SQL query and a tuple of
> parameters. The query is stored inside the function as a triple-quoted
> string, and the parameters are derived depending on the input arguments.
>
> Sometimes while testing
On 30/03/20, Stefan Knecht (knecht.ste...@gmail.com) wrote:
> Rory, this is about established connections, not new connections - psycopg2
> already offers a connection timeout, but that is a different thing. I don't
> want to drift too far off topic - but we are already using pgbouncer, and
> the p
On 30/03/20, Stefan Knecht (knecht.ste...@gmail.com) wrote:
> If I may, one thing that has been a constant troublemaker for us - running
> primarily on AWS - is timeouts.
If the issue is disappearing hosts or general connectivity problems,
isn't that problem best dealt with by pg_bouncer?
https:
On 04/10/18, Daniele Varrazzo (daniele.varra...@gmail.com) wrote:
> The feature I'm the most excited about (and worried about its
> reception) is to raise a different exception for every postgres error
> message (see #682) . For instance `SELECT * FROM wrong_name` will
> raise `UndefinedTable` rath
12 matches
Mail list logo
