pypgsql-users — Discussion list for the pyPgSQL user community.

Re: [Pypgsql-users] executemany question

[<gh...@gh...>]

Steve Waterbury wrote:
> I may be misunderstanding the purpose of
> cursor.executemany(query, sequence_of_params) ...
> 
> The doc says "Execute a query many times, once
> for each params in the sequence."  I had hoped
> the results would accumulate in the cursor, but
> it doesn't appear to (perhaps I'm doing something
> wrong!).  Here's what I'm doing:
> 
> curs.executemany('select * from docs where doc_number = %s', docnums)

executemany is not supposed to be used with SELECTs. Use it for INSERT 
or UPDATE only.

> in which docnums is a list of strings, which are
> values of doc_number.  (I've verified that they are
> valid.)  Then when I then do
> 
> curs.fetchall()
> 
> ... I get only the result of the execution of the query
> using the last item in the list (which is certainly what
> you get by doing several "execute(query, parms)"
> in succession).
> 
> Is this the way it's supposed to work?
> 
> And if so, what would be a good way of doing what I want to
> do (i.e., feed in a sequence of parameters and get
> back a cumulative result of executing the same
> query with each one)? [...]

In your particular example:

docnums = [3,4,5,6]
curs.execute("select * from docs where doc_number in %s", (docnums,))

Other problems will require other solutions.

-- Gerhard

[Pypgsql-users] executemany question

[Steve W. <go...@co...>]

I may be misunderstanding the purpose of
cursor.executemany(query, sequence_of_params) ...

The doc says "Execute a query many times, once
for each params in the sequence."  I had hoped
the results would accumulate in the cursor, but
it doesn't appear to (perhaps I'm doing something
wrong!).  Here's what I'm doing:

curs.executemany('select * from docs where doc_number = %s', docnums)

in which docnums is a list of strings, which are
values of doc_number.  (I've verified that they are
valid.)  Then when I then do

curs.fetchall()

... I get only the result of the execution of the query
using the last item in the list (which is certainly what
you get by doing several "execute(query, parms)"
in succession).

Is this the way it's supposed to work?

And if so, what would be a good way of doing what I want to
do (i.e., feed in a sequence of parameters and get
back a cumulative result of executing the same
query with each one)?

Should I just loop over execute() calls in my code and
do my own accumulation?

TIA!
Steve.

RE: [Pypgsql-users] [PATCH] Memory leak in libPQquoteBytea@libpqm odule.c

[Pinchart, L. <Pin...@PC...>]

> It's not a memory leak, it's a potential buffer overrun, right?

Right, sorry. I'm not fully awake yet :-)

Laurent Pinchart

Re: [Pypgsql-users] [PATCH] Memory leak in libPQquoteBytea@libpqmodule.c

[<gh...@gh...>]

Laurent,

thanks for the patch. Just want to assure I'm not missing something:

Pinchart, Laurent wrote:
> Here's a patch that fixes a memory leak in libPQquoteBytea@libpqmodule.c.

It's not a memory leak, it's a potential buffer overrun, right?

> Bytea are quoted using as much as 5 bytes per input byte (0x00 is quoted
> '\\000'), so allocating (slen * 4) + 3 is not enough for data that contain
> lots of 0x00 bytes.
> 
> The patch has been tested on Windows, with PyPgSQL compiled with VS6.

-- Gerhard

[Pypgsql-users] [PATCH] Memory leak in libPQquoteBytea@libpqmodule.c

[Pinchart, L. <Pin...@PC...>]

Here's a patch that fixes a memory leak in libPQquoteBytea@libpqmodule.c.

Bytea are quoted using as much as 5 bytes per input byte (0x00 is quoted
'\\000'), so allocating (slen * 4) + 3 is not enough for data that contain
lots of 0x00 bytes.

The patch has been tested on Windows, with PyPgSQL compiled with VS6.

Laurent Pinchart

RE: [Pypgsql-users] PyPgSQL 2.3 build problems under Windows

[Pinchart, L. <Pin...@PC...>]

> The information you need should be in README.win32 in the 
> pyPgSQL source distribution.

Thanks for your help. I found the information I needed.

> If you have any further questions, just ask. I'd be glad if 
> finally I'd not be the only one who actually builds on native
> Windows :-)

I have to build on native Windows but I don't like it.

I've been able to build PyPgSQL-2.3 with Visual Studio 6. It builds under
Visual Studio .NET too, but crashes somewhere in the DLL initialization
code. Seems to be a memory problem (the crash seems to occur in one of the
Rtl*Alloc functions in NTDLL).

Anyway, Windows is only for development computers, the target is Linux :-)

Laurent Pinchart

Re: [Pypgsql-users] Re: Does anyone use SuSE 8.2

[<gh...@gh...>]

[Still cc-ing to pypgsql-users so that this is documented in the right 
place]

John Fabiani wrote:
> The output from ldd is as follows:
>         libpq.so.2 => not found
>         libc.so.6 => /lib/libc.so.6 (0x40027000)
>         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
> The output from ls is as follows:
> lrwxrwxrwx    1 root     root           12 2003-05-29 09:22
> /usr/lib/libpq.so.3 -> libpq.so.3.0
> -rwxr-xr-x    1 root     root        96044 2003-03-17 07:57
> /usr/lib/libpq.so.3.0

You can try to create the appropriate symlink:

ln -s /usr/lib/libpq.so.3.0 /usr/lib/libpq.so.2

but I'm not sure this really works.

I'd recommend to compile from sources instead.

> It appears I have the wrong libraries - right?

Yes.

> So (I'm guessing) how do I compile the source?
> 
> I noticed that the tar file has setup.py (but that does not work).

Sorry, but "Does not work" is a much too incomplete description of the 
problem.

> You'll have to walk through this process.

First you need to have the appropriate packages installed. I reckon gcc 
and postgresql-devel should be enough.

If you still have problems building, please post the complete output of 
"python setup.py build".

ciao,

-- Gerhard

Re: [Pypgsql-users] PyPgSQL 2.3 build problems under Windows

[<gh...@gh...>]

Pinchart, Laurent wrote:
> Hi everybody,
> 
> I'm having problems with PyPqSQL 2.3 under Windows. I have PostgreSQL 7.3.2
> installed (in Cygwin), and I'm trying to build PyPgSQL.
> 
> I tried to run setup.py using a Windows version of Python (2.2.2) in a
> Windows command shell. After unpacking PostgreSQL in ../postgresql, it
> failed at the linker stage, complaining about a missing pq.lib.
> 
> I then tried to compile PostgreSQL 7.3.2 (in Cygwin), but no pq.lib is
> generated by the build process.
> 
> I can build PyPgSQL in Cygwin, but I then get a DLL that depends on
> cygwin1.dll. I would like to get the same result as the binary PyPgSQL
> package (libpq.pyd that doesn't depend on Cygwin).
> 
> Thanks in advance for all the help you can provide.

The information you need should be in README.win32 in the pyPgSQL source 
distribution.

If you have any further questions, just ask. I'd be glad if finally I'd 
not be the only one who actually builds on native Windows :-)

-- Gerhard

[Pypgsql-users] PyPgSQL 2.3 build problems under Windows

[Pinchart, L. <Pin...@PC...>]

Hi everybody,

I'm having problems with PyPqSQL 2.3 under Windows. I have PostgreSQL 7.3.2
installed (in Cygwin), and I'm trying to build PyPgSQL.

I tried to run setup.py using a Windows version of Python (2.2.2) in a
Windows command shell. After unpacking PostgreSQL in ../postgresql, it
failed at the linker stage, complaining about a missing pq.lib.

I then tried to compile PostgreSQL 7.3.2 (in Cygwin), but no pq.lib is
generated by the build process.

I can build PyPgSQL in Cygwin, but I then get a DLL that depends on
cygwin1.dll. I would like to get the same result as the binary PyPgSQL
package (libpq.pyd that doesn't depend on Cygwin).

Thanks in advance for all the help you can provide.

Laurent Pinchart

Re: [Pypgsql-users] Re: Does anyone use SuSE 8.2

[<gh...@gh...>]

Gaston Droguett wrote:
> [pyPgSQL RPM does not run on SuSE 8.2]
> Try puting a file called whatever.pth in site-package
> directory and inside you must write the name of the
> subdirectory you need to look in.

No. That's definitely not needed for the pyPgSQL RPM.

It's most likely a problem with minor versions of PostgreSQL's ilbpq 
RPM. They changed that from Pg 7.3 to Pg 7.3.1 AFAIR. A symbolic link 
*could* help, but I need the information I asked for to judge that.

-- Gerhard

Re: [Pypgsql-users] Re: Does anyone use SuSE 8.2

[<gdr...@ya...>]

 --- Gerhard_Häring <gh...@gh...> escribió: > John
Fabiani wrote:
> > Hi,
> > 
> > I'm having lots of trouble getting pyPgSQL and
> PythonCard running.  My
> > python is 2.2.2 and appears to be in the same
> location as RH
> > "/usr/lib/python2.2/site-packages/" but I can't
> get anything to run.  I was
> > succesful with wxPython but that's all.  When I
> attempt to "from libpg
> > import *". I get file "libpg" not found.  But it
> is in
> > site-packages/pyPgSQL - so I don't know what's
> happening.  
> > -- So I'm in need of help.
> 
> I'll be able to help (though I don't use SuSE myself
> any longer).
> 
> If you want it to get running fast, compile pyPgSQL
> yourself and don't 
> try to use a Redhat RPM on a SuSE machine. That's
> really not difficult, 
> just be sure you have the required packages
> installed and follow the 
> instructions in the README file in the source
> distribution.
> 
> Apart from that, I believe you don't have the
> version of the PostgreSQL 
> client libraries installed that the pyPgSQL RPM
> references.
> 
> Please post the output of:
> 
> ldd
>
/usr/lib/python2.2/site-packages/pyPgSQL/libpq/libpqmodule.so
> 
> and
> 
> ls -al /usr/lib/libpq.so*
> 
> -- Gerhard
> 
> PS: I'd recommend to use a subject next time that
> gives people an idea 
> what the message is about. Normally I'd overlook
> posts like this, while 
> I will read all with pyPgSQL in the subject.
> 



Hello:

Try puting a file called whatever.pth in site-package
directory and inside you must write the name of the
subdirectory you need to look in.

for example:
I have a module called x.py in site-package/mydir/ 
To reach it  I have a file called mydir.pth in
site-package/
the file mydir.pth contains a line with:

mydir

This tells python to look inside mydir directory to
find a module.
That will work for now.

Gaston 

_________________________________________________________
Do You Yahoo!?
Información de Estados Unidos y América Latina, en Yahoo! Noticias.
Visítanos en http://noticias.espanol.yahoo.com

Re: [Pypgsql-users] Re: Does anyone use SuSE 8.2

[Karsten H. <Kar...@gm...>]

>> succesful with wxPython but that's all.  When I attempt to "from libpg
>> import *". I get file "libpg" not found.  But it is in
Well, for one thing it needs to be 

libpQ (libpq) not libpG (libpg)

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

[Pypgsql-users] Re: Does anyone use SuSE 8.2

[<gh...@gh...>]

John Fabiani wrote:
> Hi,
> 
> I'm having lots of trouble getting pyPgSQL and PythonCard running.  My
> python is 2.2.2 and appears to be in the same location as RH
> "/usr/lib/python2.2/site-packages/" but I can't get anything to run.  I was
> succesful with wxPython but that's all.  When I attempt to "from libpg
> import *". I get file "libpg" not found.  But it is in
> site-packages/pyPgSQL - so I don't know what's happening.  
> -- So I'm in need of help.

I'll be able to help (though I don't use SuSE myself any longer).

If you want it to get running fast, compile pyPgSQL yourself and don't 
try to use a Redhat RPM on a SuSE machine. That's really not difficult, 
just be sure you have the required packages installed and follow the 
instructions in the README file in the source distribution.

Apart from that, I believe you don't have the version of the PostgreSQL 
client libraries installed that the pyPgSQL RPM references.

Please post the output of:

ldd /usr/lib/python2.2/site-packages/pyPgSQL/libpq/libpqmodule.so

and

ls -al /usr/lib/libpq.so*

-- Gerhard

PS: I'd recommend to use a subject next time that gives people an idea 
what the message is about. Normally I'd overlook posts like this, while 
I will read all with pyPgSQL in the subject.

Re: [Pypgsql-users] Re: postgresql notifications

[Billy G. A. <bil...@mu...>]

Gerhard H=E4ring wrote:

> [Cc-ed to pypgsql-users - I'd recommend to take this discussion over=20
> there]
>
> Witek wrote:
>
>> Gerhard H=E4ring wrote:
>>
>>>> I'm using pypgsql to connect to postgresql database (7.2, 7.3).
>>>> I recieve PgNotify object using notifies() method of connection=20
>>>> object, but it's fields values are random chars and wrong process=20
>>>> id. Is there someone, who put it to work?
>>>
>>>
>>> The pyPgSQL source distribution includes examples for notifications=20
>>> (examples/demo2a.py, examples/demo2b.py).
>>> Please report back if you still have problems.
>>
>>
>> They are not working under Linux or Windows. I tried examples from=20
>> gnumed project as well.
>
>
> They did certainly work for me last time I checked.
>
> Do you have different versions of the PostgreSQL client library and=20
> the server? If for example you use a 7.3 client and a 7.2 server there=20
> might be some problems ... Just a rough guess of me of course.
>
> -- Gerhard

It was working the last time I checked, but it's not working now :-(
I've update the CVS repository with a fixed pgnotify.c that will correct=20
the problem.  I am also attaching a patch file to correct the problem.

--=20
_________________________________________________________________________=
__
____       | Billy G. Allie    | Domain....: Bil...@mu...
|  /|      | 7436 Hartwell     | MSN.......: B_G...@em...
|-/-|----- | Dearborn, MI 48126|
|/  |LLIE  | (313) 582-1540    |

Re: [Pypgsql-users] Re: postgresql notifications

[Adam B. <ad...@po...>]

On Wed, May 28, 2003 at 02:18:42PM +0200, Gerhard H=E4ring wrote:
> >>The pyPgSQL source distribution includes examples for notifications=20
> >>(examples/demo2a.py, examples/demo2b.py).
> >>Please report back if you still have problems.
[...]
> They did certainly work for me last time I checked.
>=20
> Do you have different versions of the PostgreSQL client library and the=
=20
> server? If for example you use a 7.3 client and a 7.2 server there migh=
t=20
> be some problems ... Just a rough guess of me of course.

I quickly checked my installation of PostgreSQL + pyPgSQL and NOTIFY
messages do not work either.  I have Python 2.2.2, PostgreSQL 7.3.2
and pyPgSQL 2.3, everything compiled and installed from sources.  The
problem is that although NOTIFY messages are sent to the client, thay
are not correctly decoded by pyPgSQL library.

The result of running demo2a and demo2b is:

Waiting.....
ASYNC NOTICE of 'P*' from backend pid 1066 recieved
Waiting.....
ASYNC NOTICE of '*' from backend pid 1066 recieved
Waiting...........
ASYNC NOTICE of 'P*' from backend pid 1066 recieved

The string 'P*' or '*' is random and each run of demo programs shows
something different here.  Sometimes these characters are even
non-ASCII.  Everything works under plain psql, however: when I run
demo2b, psql prints:

Asynchronous NOTIFY 'demo2a' from backend with pid 1089 received.
Asynchronous NOTIFY 'demo2a' from backend with pid 1089 received.
Asynchronous NOTIFY 'demo2a' from backend with pid 1089 received.

Regards,

--=20
Adam Buraczewski <ad...@po...> * Linux registered user #165585
GCS/TW d- s-:+>+:- a- C+++(++++) UL++++$ P++ L++++ E++ W+ N++ o? K? w--
O M- V- PS+ !PE Y PGP+ t+ 5 X+ R tv- b+ DI? D G++ e+++>++++ h r+>++ y?

Re: [Pypgsql-users] Re: postgresql notifications

[Karsten H. <Kar...@gm...>]

>> They are not working under Linux or Windows. I tried examples from 
>> gnumed project as well.
I wrote most of the GnuMed code and it certainly works for me.
If you run client/python-common/gmPG.py from our CVS you'll be
asked if you want to run a PostgreSQL notification debugger
shell. You can use one or two of those to test various
scenarios or mix in some psql sessions, too.

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

[Pypgsql-users] Re: postgresql notifications

[<gh...@gh...>]

[Cc-ed to pypgsql-users - I'd recommend to take this discussion over there]

Witek wrote:
> Gerhard Häring wrote:
> 
>>> I'm using pypgsql to connect to postgresql database (7.2, 7.3).
>>> I recieve PgNotify object using notifies() method of connection 
>>> object, but it's fields values are random chars and wrong process id. 
>>> Is there someone, who put it to work?
>>
>> The pyPgSQL source distribution includes examples for notifications 
>> (examples/demo2a.py, examples/demo2b.py).
>> Please report back if you still have problems.
> 
> They are not working under Linux or Windows. I tried examples from 
> gnumed project as well.

They did certainly work for me last time I checked.

Do you have different versions of the PostgreSQL client library and the 
server? If for example you use a 7.3 client and a 7.2 server there might 
be some problems ... Just a rough guess of me of course.

-- Gerhard

Re: [Pypgsql-users] Will pypgsql serve PGSQL7.4 on Windows?

[<gh...@gh...>]

ze...@in... wrote:
> I wanna begin an adventure with PostgreSQL and pypgsql on Windows.

The only available native win32 version of PostgreSQL was some beta I 
once got a link for by the company that did the win32 port. It's based 
on 7.2. This company killed the win32 port shortly before it got 
completed if I remember the postings on postgresql-dev correctly.

Right now Bruce Momjan and the original win32 porter (who left the 
company in the meanwhile, "left" being an euphemism ...) are working on 
getting the win32 stuff ready before PostgreSQL 7.4 beta, which is 
scheduled for July 1.

PostgreSQL 7.4 beta will also feature a new FE/BE protocol, and the 
server will use this protocol. The client will support the new and the 
old protocols.

If I'm not mistaken this will mean that you'll have to recompile pyPgSQL 
against the 7.4 client libraries to be able to access 7.4 servers.

It's also not entirely sure if the win32 stuff will be ready for beta 
testing until July 1. If it isn't, it will be deferred for PostgreSQL 
7.5. Same for PITR.

> I've read that pypgsql doesn't work with native windows version of PostgreSQL. 

Where have you read that?

> But probably already on 1 July will be released new version of PGSQL-7.4 , which will work on Windows without installing cygwin.

Hopefully.

> I dont wanna installing cygwin so I'am interested if this new version of PGSQL will work with pypgsql on windows (if yes on which versions of Windows). I realize that my query may be a little premature, but who knows - maybe for somebody answer is simple today.

Fortuntely, compiling pyPgSQL on Windows is relatively easy, so you 
could do that yourself when the beta comes out. Chances are I'll try to 
do that myself, though and I might provide testing pyPgSQL binaries for 
7.4 beta.

-- Gerhard

[Pypgsql-users] Will pypgsql serve PGSQL7.4 on Windows?

[<ze...@in...>]

I wanna begin an adventure with PostgreSQL and pypgsql on Windows.
I've read that pypgsql doesn't work with native windows version of PostgreS=
QL. But probably already on 1 July will be released new version of PGSQL-7.=
4 , which will work on Windows without installing cygwin.

I dont wanna installing cygwin so I'am interested if this new version of PG=
SQL will work with pypgsql on windows (if yes on which versions of Windows)=
. I realize that my query may be a little premature, but who knows - maybe =
for somebody answer is simple today.

With best regards=20
Robert Kolo

[Pypgsql-users] serializable and exceptions

[Karsten H. <Kar...@gm...>]

Dear all,

any chance we will see a dedicated exception for a "can't
serialize" error in transaction isolation level "serializable" ?

It is essentiel to be able to know when that condition occurs
as opposed to other failure causes as one wants to retry the
transaction in that case. Right now one would have to
pattern-match the message delivered with the exception.

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

[Pypgsql-users] pyPgSQL build problem under Python 2.3b1

[Andrew M. <an...@ob...>]

It would appear that LONG_LONG has been renamed
PY_LONG_LONG in Python 2.3b1. My quick and dirty
fix was to add this to libpqmodule.h:


diff -u -r x/pypgsql/libpqmodule.h pypgsql/libpqmodule.h
--- x/pypgsql/libpqmodule.h     2002-10-07 16:03:46.000000000 +1000
+++ pypgsql/libpqmodule.h       2003-05-16 09:49:16.000000000 +1000
@@ -108,6 +108,10 @@

 void *PyMem_Strdup(void *);

+#ifdef PY_LONG_LONG
+#define LONG_LONG PY_LONG_LONG
+#endif
+
 #ifdef __cplusplus
 }
 #endif

Re: [Pypgsql-users] insert tuples through copy

[Billy G. A. <bil...@mu...>]

Gaston Droguett wrote:

>Hello:
>Im trying to insert tuples through the copy sql like
>this:
>
>curs.execute('copy tablename from stdin;')
>curs.execute('2\t3\4\n')
>
>I get an error:
>    self.res = self.conn.conn.query(_qstr)
>libpq.ProgrammingError: COPY state must be terminated
>first
>
>I can't find the way to send the tuples string.
>
>In C you can do the following:
>
>PQexec(conn,"copy foo from stdin");
>PQputline(conn,"3\t4\n");
>PQputline(conn,"\\.\n";
>PQendcopy(conn);
>
>
>How can this be done with PgSQL??
>  
>
The PQputline and PQendcopy are exposed in the libpq PgConnection object 
as putline and endcopy.
The underlying libpq.PgConnection object is exposed as curs.conn.conn.
What you want to accomplish can be done as:

curs.execute('copy tablename from stdin')
curs.conn.conn.putline('2\t3\tr\n')
...
curs.conn.conn.endcopy()

In general, if there is something you want to do that is not supported 
by the DB-API 2.0 specification that PgSQL follows, but you would be 
able to do with th e libpq C API, then you can do it using the libpq 
module that PgSQL is built upon.  The libpq module exposes (most of) the 
C API available in the libpq library.

I hope this helps.

-- 
___________________________________________________________________________
____       | Billy G. Allie    | Domain....: Bil...@mu...
|  /|      | 7436 Hartwell     | MSN.......: B_G...@em...
|-/-|----- | Dearborn, MI 48126|
|/  |LLIE  | (313) 582-1540    |

[Pypgsql-users] insert tuples through copy

[<gdr...@ya...>]

Hello:
Im trying to insert tuples through the copy sql like
this:

curs.execute('copy tablename from stdin;')
curs.execute('2\t3\4\n')

I get an error:
    self.res = self.conn.conn.query(_qstr)
libpq.ProgrammingError: COPY state must be terminated
first

I can't find the way to send the tuples string.

In C you can do the following:

PQexec(conn,"copy foo from stdin");
PQputline(conn,"3\t4\n");
PQputline(conn,"\\.\n";
PQendcopy(conn);


How can this be done with PgSQL??



_________________________________________________________
Do You Yahoo!?
Información de Estados Unidos y América Latina, en Yahoo! Noticias.
Visítanos en http://noticias.espanol.yahoo.com

Re: [Pypgsql-users] Strange phenomenon?

[Dick K. <D.J...@ch...>]

Hi Billy/list,

It was just a stupd mistake. Small change, now it works.....

Thanks for your assistence

Kind regards

On Thu, 2003-05-01 at 05:21, Billy G. Allie wrote:
> Dick Kniep wrote:
> 
> >Hi List,
> >
> >The last 6 month I have been developing a system with Python, wxPython
> >and pyPgSQL. I use Python 2.2.2, PostgreSQL 7.3.2 (the latest) and
> >pyPgSQL 2.3
> >
> >Mostly, it works great. Thanks to all contributors.
> >
> >However, lately I saw a strange phenomenon. When I use the following
> >select statement :
> >
> >Select last-value from tabellen_tab-id_seq;
> >
> >where tabellen_tab-id_seq is a Postgresql sequence, I get back a number
> >followed by an 'L' so in this case the result was 
> >[547L]. Obviously this fails in the rest of my code, because I expect an
> >integer.
> >
> >I think it might have something to do with the fact that in PostgreSQL
> >this is an 8 byte int, but I am not sure....
> >  
> >
> This is strage.  The result of a serial8 field should be a BIGINT, which 
> is handled as a PgInt8 type.
> Does your system have native 8-byte int (long long) support.  If not the 
> BIGINTs are supported
> using Python's Long integer type (hence the L at the end of the number).
> 
> How is the long integer failing in the rest of your code?  Printing the 
> value will not display the 'L'.
> Using the str() function on the number will not place an 'L' in the 
> resulting string.  The only time
> the 'L' is display is in the result of using the repr() function on the 
> number, so how is your code
> failing? (If I know how it's failing I may be able to help fix it.)
> 
> -- 
> ___________________________________________________________________________
> ____       | Billy G. Allie    | Domain....: Bil...@mu...
> |  /|      | 7436 Hartwell     | MSN.......: B_G...@em...
> |-/-|----- | Dearborn, MI 48126|
> |/  |LLIE  | (313) 582-1540    |
> 
> 

[Pypgsql-users] [Fwd: Please forward to pypgsql-users list.]

[Billy G. A. <bil...@mu...>]

-- 
___________________________________________________________________________
____       | Billy G. Allie    | Domain....: Bil...@mu...
|  /|      | 7436 Hartwell     | MSN.......: B_G...@em...
|-/-|----- | Dearborn, MI 48126|
|/  |LLIE  | (313) 582-1540    |