logo       

Re: [psycopg] #100: null pointer: msg#00010

python.db.psycopg.devel

Subject: Re: [psycopg] #100: null pointer

#100: null pointer
-----------------------------------------+----------------------------------
Reporter: brian AT equal / ed DOT net | Owner: fog
Type: defect | Status: closed
Priority: high | Milestone: PSYCOPG 2.0
Component: psycopg2 | Version: 2.0beta
Severity: critical | Resolution: invalid
Keywords: |
-----------------------------------------+----------------------------------
Changes (by fog):

* resolution: => invalid
* status: new => closed

Comment:

COPY TO/COPY FROM require some help from the driver and are implemented
using the .copy_from() and .copy_to() cursor methods.

What could be done is to rise the right kind of exception if someone tries
to directly execute a COPY command but '''some''' kinds of COPY statements
are perfectly sane (only STDIN/STDOUT need help from the driver). So I am
closing this bug as it is not a bug.

Btw, posting a report full of Python exceptions, without explanations and
setting it at high/critical is the wrong way to have me fix it in a short
time. :)

--
Ticket URL: <http://initd.org/tracker/psycopg/ticket/100>
psycopg <http://initd.org/>
psycopg_______________________________________________
Psycopg mailing list
Psycopg-IAPFreCvJWPBWskQ1e/+sw@xxxxxxxxxxxxxxxx
http://lists.initd.org/mailman/listinfo/psycopg
<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise