Activity (RSS)

There is a minor typo in setup.cfg.

I have attached a patch that fixes it, and also removes some extraneous whitespace.

There are a few minor typos in the project's INSTALL document.

I have attached a patch against the devel branch that fixes them, and removes some extraneous whi...

Hi, sorry for the delay. I've been away for a while and wanted to double check by compiling on Solaris8 as well (we ended up dropping it early so it's no longer...

Floris Bruynooghe updated this ticket at February 8th, 2012 @ 01:47 PM

Hi, I must admit I've been guilty of submitting the patch before running it on our build...

Re: [psycopg #97] Provide missing round function for solaris 8 & 9

Hi, I must admit I've been guilty of submitting the patch before running it on our build system (I did submit this in the middle between an upgrade from 3.4.2 t...

Hello Floris, thank you for the patch, it's very welcome.

I've found in http://wiki.opencsw.org/porting-faq that there should be constants to detect the SunOS v...

The previously attached patch was for 2.4.2, sorry about that. This one is updated for 2.4.4.

The config.h file contains a round() function to use when the platform is missing it. However the conditions assume solaris has round. On our servers we found o...

After some thoughts, I agree that enhancment it would provide would be supressed by backward incompatibilitiy issues, so leaving it as it is, is the best choice...

The pgcode may be important, but I suspect now it would mostly break other people code (only at visualization level, but knowing from the past I'd say it would ...

Daniele,

Pros:
* When you log exception, you see also pgcode, which may be important (error messages can change, while pgcode should remain unchanged (user's st...

If we put stuff in args, it ends up being printed everywhere, changing the current behaviour of the exception:

In [1]: class MyException(Exception): pass
   .....

Sorry, I haven't used git much outside of "git svn".

Thanks for taking the changes.

Committed. Note that your patches fails to apply with "git am", so I have to do some copypaste to keep the attribution: it would be great if you could use git f...

Oops, patched attached now.

Merged, thank you!

Why it would be handy? Can you make an example? Thanks.

Thanks Menno, but you forgot to apply the patch! :)

Applied, thanks.

Now only exception message is present in exception.args.
It would be handy if pgcode was passed to Psycopg2 exception constructor, so it would be available in e...

The attached patch avoids creating a new FixedOffsetTimezone instance if one with the same offset and name has been created before. This will save memory when r...

For offsets west of UTC the repr of FixedOffsetTimezone shows a positive and confusing offset value. The offset used during passed to init is not the offset sho...

One of the tests in test_dates.py has a name which collides with another test. The trivial patch attached fixes the issue. The shadowed test was perfectly valid...

I think it an expected behaviour: PostgreSQL internally uses mostly - or maybe uniquely - zero-terminated strings when dealing with text: only bytea can store z...

I'm using version 2.3.2 with postgres 9.0. I apologize if this has been addressed already.

I'm making use of the NOTIFY command and was recently doing some test...

Fixed in my branch.

Ok, nice you have fixed the problem.

The cursors are not thread safe: you did good to use a different one for each thread. It would be nice if they didn't crash...

Yes, the message on http://bugs.python.org/issue13741 was mine. I seem to have fixed the problem though. In the version that crashed, all the clients (there's a...

Agreed.

With some google-fu I've found: http://bugs.python.org/issue13741 with the additional info:

This program crashes after 12-24 hours of running.  My OS is Ubuntu...

Is this example self-contained?

Submitted by: BlendsInWell

Here's the error:
glibc detected /usr/bin/python: double free or corruption (!prev): 0x0000000001c24710 *** ======= Backtrace: ======...

Yeah, makes entirely sense.

I think it would be fine if we set cursor to None on pickle: because of the exception, we can say nobody has ever used pickle + exce...

They are because when the exception propagates up the call stack you may want to issue a ROLLBACK from a piece of code that doesn't have an easy way to obtain t...

Uhm... reading back, I see what you mean. Sorry, I see now you just want to pickle the exception.

I think it can be done if the cursor is dropped from it. Will ...

It's not possible to pickle a connection nor a cursor because the connection wraps an open socket, which has a state that can't be pickled. It's not just a prob...

import psycopg2
conn = psycopg2.connect("dbname='somedb'")
cur = conn.cursor() 
try:
    cur.execute("SELECT * FROM barf")
except Exception, e:
    print e
   ...

Patch merged, thanks.

Hi Giovanni,

would you mind raising the question to the mailing list? It will get a much wider attention, including pgpool developers and people who know better...

No, I don't think it is a good idea: it saves you a single line of code (which is not the design guideline of python systems) at the expense of writing code tha...

Is it a good idea to add an "execute()" method on the Connection object, to avoid calling the "cursor()" and then an "cursor.execute()" method ?

I know it's non...

cursor.next() is not part of the public interface, but an implementation detail: the cursor is iterable (you can call iter() on it), the fact it is also an iter...

As it says on the tin, RealDictCursor is "extremely specialized and does not allow the normal access (using integer indices) to fetched data". It basically viol...

Thank you for reporting. Fixed in my devel branch.

Hi.

I'm using psycopg2 against a PostgreSQL database replicated using pgpool-II. On this database I also need large objects support. Apparently pgpool-II is abl...

Yup: fixed in 2.4.3.