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

Re: [Pypgsql-users] pypgsql and postgresql 8

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

> If I've read this correctly the implication is that PyPgSQL is not really
> going to be maintained any longer.
STOP ! No !

I am just a user of PyPgSQL - same as the other people in this
thread. I did not want to say that pyPgSQL won't be maintained
any longer (I couldn't say that even if I wanted) but rather
that to me maintenance has seemed OK but slow. I also said
that there may be valid reasons for that.

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

RE: [Pypgsql-users] pypgsql and postgresql 8

[jose <jo...@cy...>]

If I've read this correctly the implication is that PyPgSQL is not =
really
going to be maintained any longer.  Bummer really it is a very nice
interface.  If it is not going to be maintained, is there any
recommendations as to which API to switch to?

Jose



-----Original Message-----
From: pyp...@li...
[mailto:pyp...@li...] On Behalf Of Karsten
Hilbert
Sent: Wednesday, January 19, 2005 1:11 AM
To: pyp...@li...
Subject: Re: [Pypgsql-users] pypgsql and postgresql 8


> while testing postgresql 8 i was wondering if s.b. could provide some=20
> info if there are plans to finish an updated version of pypgsql which=20
> works with postgresql 8.
I assume you mean "takes advantage of the new binary protocol" ? I =
second
that interest.

Due to slow support (which may have very legitimate reasons) I have
considered moving GnuMed to another DB-API module. Doing so will likely =
make
our code more generic and thus switching back easier if later we ever so
desire. We are already carrying a patch and a workaround in our CVS tree
that apparently don't make it into pyPgSQL proper. A second patch is on =
the
way in. All of them were posted on this list.

PyPgSQL has served us well so far, however, including delivering =
NOTIFYs.

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


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE
limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and =
FREE --
well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Pypgsql-users mailing list
Pyp...@li...
https://lists.sourceforge.net/lists/listinfo/pypgsql-users

Re: [Pypgsql-users] pypgsql and postgresql 8

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

> while testing postgresql 8 i was wondering if s.b. could
> provide some info if there are plans to finish an updated version
> of pypgsql which works with postgresql 8. 
I assume you mean "takes advantage of the new binary protocol" ?
I second that interest.

Due to slow support (which may have very legitimate reasons) I
have considered moving GnuMed to another DB-API module. Doing
so will likely make our code more generic and thus switching
back easier if later we ever so desire. We are already carrying
a patch and a workaround in our CVS tree that apparently don't
make it into pyPgSQL proper. A second patch is on the way in.
All of them were posted on this list.

PyPgSQL has served us well so far, however, including
delivering NOTIFYs.

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

[Pypgsql-users] pypgsql and postgresql 8

[Chris S. <c.s...@ar...>]

hello,

while testing postgresql 8 i was wondering if s.b. could
provide some info if there are plans to finish an updated version
of pypgsql which works with postgresql 8. 

thanks very much in advance.

cheers

chris

Re: [Pypgsql-users] Dictionary Cursor?

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

> > The default cursor works like both the DB-API cursor and MySQLdb's
> > DictCursor. Try it :-)
> Ha!  Imagine that.  I completely looked over that aspect of it.
Be aware how, AFAIK, that is not DB-API compliant, though.

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

Re: [Pypgsql-users] Dictionary Cursor?

[Jon-Pierre G. <jg...@se...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Gerhard Haering wrote:

>>I was curious as to whether or not anyone has attempted to implement
>>a cursor that returns a dictionary keyed from column names, similar
>>to the MySQLdb.DictCursor class?  I am not familiar enough with libpg
>>to implement it myself.
> 
> 
> The default cursor works like both the DB-API cursor and MySQLdb's
> DictCursor. Try it :-)

Ha!  Imagine that.  I completely looked over that aspect of it.

Thank you very much!


- --
_________________________________________________________

  Jon-Pierre Gentil               PGP: 0xA21BC30E
  jabber: jg...@se...    web: www.sebistar.net
  "If you think education is expensive, try ignorance."
_________________________________________________________
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iEYEAREDAAYFAkHlyBsACgkQOrVFmaIbww5XAgCgmaClLTvB8wcbpJx29Agv943o
o/MAoL9WQb0lKYUsmuPmhR9YDXFzvRLm
=0KBT
-----END PGP SIGNATURE-----

Re: [Pypgsql-users] problem with invalid characters

[Timothy S. <ti...@op...>]

Karsten Hilbert wrote:

>>>>i'm wondering why i get the following error witht he code below
>>>>i'm guessing it's probably somethign very simple i'm goign wrong, most 
>>>>likely to do with my new line escapes \
>>>>if there is a better way of formatting my query to fix this i'm all ears.
>>>>  
>>>>
>>>>        
>>>>
>>>consider using
>>>
>>>query = """
>>>... any formatting you want
>>>"""
>>>
>>>No \ needed.
>>>
>>>Karsten
>>>
>>>
>>>      
>>>
>>ok i did that b ut i still get the error
>>
>>cur.execute("""CREATE OR REPLACE FUNCTION week_num ( date )
>> File "/usr/local/lib/python2.3/site-packages/pyPgSQL/PgSQL.py", line 
>>3072, in execute
>>   raise OperationalError, msg
>>libpq.OperationalError: ERROR:  syntax error at or near "20040701" at 
>>character 92
>>    
>>
>The error seems to be in the first function declaration. In
>there you have the %s *inside* the actual function body. I
>doubt that pyPgSQL knows about the proper quoting rules for
>that case, eg quotes need to be doubled at least, even tripled
>or quadrupled in some special cases.
>
>Karsten
>  
>
your right, it needed '%s'

Re: [Pypgsql-users] problem with invalid characters

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

> >>i'm wondering why i get the following error witht he code below
> >>i'm guessing it's probably somethign very simple i'm goign wrong, most 
> >>likely to do with my new line escapes \
> >>if there is a better way of formatting my query to fix this i'm all ears.
> >>   
> >>
> >consider using
> >
> >query = """
> >... any formatting you want
> >"""
> >
> >No \ needed.
> >
> >Karsten
> > 
> >
> ok i did that b ut i still get the error
> 
> cur.execute("""CREATE OR REPLACE FUNCTION week_num ( date )
>  File "/usr/local/lib/python2.3/site-packages/pyPgSQL/PgSQL.py", line 
> 3072, in execute
>    raise OperationalError, msg
> libpq.OperationalError: ERROR:  syntax error at or near "20040701" at 
> character 92
The error seems to be in the first function declaration. In
there you have the %s *inside* the actual function body. I
doubt that pyPgSQL knows about the proper quoting rules for
that case, eg quotes need to be doubled at least, even tripled
or quadrupled in some special cases.

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

Re: [Pypgsql-users] Dictionary Cursor?

[Gerhard H. <gh...@gh...>]

On Wed, Jan 12, 2005 at 10:59:18AM -0600, Jon-Pierre Gentil wrote:
> I was curious as to whether or not anyone has attempted to implement
> a cursor that returns a dictionary keyed from column names, similar
> to the MySQLdb.DictCursor class?  I am not familiar enough with libpg
> to implement it myself.

The default cursor works like both the DB-API cursor and MySQLdb's
DictCursor. Try it :-)

-- Gerhard

Re: [Pypgsql-users] problem with invalid characters

[Timothy S. <ti...@op...>]

never mind i fixed it!

Timothy Smith wrote:

> Karsten Hilbert wrote:
>
>>> i'm wondering why i get the following error witht he code below
>>> i'm guessing it's probably somethign very simple i'm goign wrong, 
>>> most likely to do with my new line escapes \
>>> if there is a better way of formatting my query to fix this i'm all 
>>> ears.
>>>   
>>
>> consider using
>>
>> query = """
>> ... any formatting you want
>> """
>>
>> No \ needed.
>>
>> Karsten
>>  
>>
> ok i did that b ut i still get the error
>
> cur.execute("""CREATE OR REPLACE FUNCTION week_num ( date )
>  File "/usr/local/lib/python2.3/site-packages/pyPgSQL/PgSQL.py", line 
> 3072, in execute
>    raise OperationalError, msg
> libpq.OperationalError: ERROR:  syntax error at or near "20040701" at 
> character 92
>
>
> code snip
>
> cur.execute("""CREATE OR REPLACE FUNCTION week_num ( date )
>                    RETURNS integer AS '
>                    SELECT ($1 - (%s::date - extract(dow from 
> %s::date)::integer + 1))/7;'
>                    LANGUAGE sql IMMUTABLE STRICT;
>                                      CREATE OR REPLACE FUNCTION eow 
> (integer)
>                    RETURNS date AS '
>                    SELECT for_date
>                    FROM transactions
>                    WHERE (transactions.for_date - (%s::date - 
> extract(dow from %s::date)::integer + 1))/7 = $1
>                       AND EXTRACT(dow FROM transactions.for_date) = 0;'
>                    LANGUAGE sql IMMUTABLE STRICT;
>                                      SELECT DISTINCT week_num(for_date),
>                       eow(week_num(for_date)),
>                       sum(dt.door_till) as door_till,
>                       sum(dt.bar) as bar,
>                       sum(dt.total) as income,
>                       sum(budget) as income_budget,
>                       sum(wages) as wages, sum(wages_budget) as 
> wages_budget,
>                       sum(reads11pm) as reads11pm,
>                       sum(door_count) as door_count,
>                       sum(dt.promo) as promo,
>                       sum(gp) as gp,
>                       (sum(dt.total) / sum(door_count))::numeric 
> (10,2) as head,
>                       sum(profit) as profit, sum(budget_profit) as 
> budget_profit,
>                       (sum(budget_profit) / sum(dt.total))::numeric 
> (10,2) as ror
>                    FROM transactions
>                       LEFT OUTER JOIN gp
>                       ON transactions.id = gp.id
>                       LEFT OUTER JOIN wages
>                       ON transactions.id = wages.id
>                       LEFT OUTER JOIN profit
>                       ON transactions.id = profit.id
>                       LEFT OUTER JOIN budgets
>                       ON transactions.id = budgets.id
>                       LEFT OUTER JOIN daily_stats
>                       ON transactions.id = daily_stats.id
>                       LEFT OUTER JOIN (SELECT t2.id, sum(CASE WHEN 
> dt.till_name LIKE 'Main Bar%%' THEN dt.cash ELSE 0 END) as bar,
>                                sum(CASE WHEN dt.till_name = 'Front 
> Door Till' THEN dt.cash ELSE 0 END) as door_till,
>                                (sum(CASE WHEN dt.till_name LIKE 'Main 
> Bar%%' THEN dt.cash ELSE 0 END) +
>                                sum(CASE WHEN dt.till_name = 'Front 
> Door Till' THEN dt.cash ELSE 0 END)) as total,
>                                sum(CASE WHEN dt.till_name = 'PR Cards' 
> OR dt.till_name = 'Other Promo' THEN dt.cash ELSE 0 END) as promo
>                            from transactions as t2, daily_takings as dt
>                            WHERE t2.id = dt.id
>                            GROUP BY t2.id
>                            ) as dt
>                        ON dt.id = transactions.id
>                       WHERE transactions.for_venue = %s
>                         AND week_num(for_date) between %s and %s
>                    GROUP BY week_num(for_date)
>                    ORDER BY week_num(for_date)"""
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Pypgsql-users mailing list
> Pyp...@li...
> https://lists.sourceforge.net/lists/listinfo/pypgsql-users
>
>

[Pypgsql-users] Connection.__del__ triggers exception under Python2.3.{3,4}

[Rune F. <run...@us...>]

I'm having a problem with pyPgSQL 2.4 under Python2.3.  When the
program terminates (normaly), a warning is triggered:

  Exception exceptions.AttributeError: "'NoneType' object has no attribute 'close'" in <bound method Connection.__del__ of <pyPgSQL.PgSQL.Connection instance at 0xb729aa8c>> ignored

Adding some verbosity in PgSQL.py:Connection shows:

   In __closeCursors, self.cursors.data.values=
     [<weakref at 0xb732a70c; to 'instance' at 0xb715e84c>]
   In __closeCursors, self.cursors.data.values=
     [<weakref at 0xb72f4f04; to 'instance' at 0xb72fd46c>]
   In __del__
   In __closeCursors, self.cursors.data.values=
     [<weakref at 0xb72f4f04; dead>]

Note that in the two last calls, the weakref has the same address.
The patch below handles this.  Please let me know if you need further
information.

--- PgSQL.py.~1.35.~	2003-07-14 23:19:20.000000000 +0200
+++ PgSQL.py	2005-01-13 00:06:42.000000000 +0100
@@ -2436,7 +2436,10 @@
 		curs = map(lambda x: x(), self.cursors.data.values())
 
 	    for i in curs:
-		if flag:
+                if i is None:
+                    pass    # reference is dead
+		elif flag:
 		    i.close()
 		else:
 		    i._Cursor__reset()

Regards,
Rune Frøysa

Re: [Pypgsql-users] problem with invalid characters

[Timothy S. <ti...@op...>]

Karsten Hilbert wrote:

>>i'm wondering why i get the following error witht he code below
>>i'm guessing it's probably somethign very simple i'm goign wrong, most 
>>likely to do with my new line escapes \
>>if there is a better way of formatting my query to fix this i'm all ears.
>>    
>>
>consider using
>
>query = """
>... any formatting you want
>"""
>
>No \ needed.
>
>Karsten
>  
>
ok i did that b ut i still get the error

 cur.execute("""CREATE OR REPLACE FUNCTION week_num ( date )
  File "/usr/local/lib/python2.3/site-packages/pyPgSQL/PgSQL.py", line 
3072, in execute
    raise OperationalError, msg
libpq.OperationalError: ERROR:  syntax error at or near "20040701" at 
character 92


code snip

cur.execute("""CREATE OR REPLACE FUNCTION week_num ( date )
                    RETURNS integer AS '
                    SELECT ($1 - (%s::date - extract(dow from 
%s::date)::integer + 1))/7;'
                    LANGUAGE sql IMMUTABLE STRICT;
                   
                    CREATE OR REPLACE FUNCTION eow (integer)
                    RETURNS date AS '
                    SELECT for_date
                    FROM transactions
                    WHERE (transactions.for_date - (%s::date - 
extract(dow from %s::date)::integer + 1))/7 = $1
                       AND EXTRACT(dow FROM transactions.for_date) = 0;'
                    LANGUAGE sql IMMUTABLE STRICT;
                   
                    SELECT DISTINCT week_num(for_date),
                       eow(week_num(for_date)),
                       sum(dt.door_till) as door_till,
                       sum(dt.bar) as bar,
                       sum(dt.total) as income,
                       sum(budget) as income_budget,
                       sum(wages) as wages, sum(wages_budget) as 
wages_budget,
                       sum(reads11pm) as reads11pm,
                       sum(door_count) as door_count,
                       sum(dt.promo) as promo,
                       sum(gp) as gp,
                       (sum(dt.total) / sum(door_count))::numeric (10,2) 
as head,
                       sum(profit) as profit, sum(budget_profit) as 
budget_profit,
                       (sum(budget_profit) / sum(dt.total))::numeric 
(10,2) as ror
                    FROM transactions
                       LEFT OUTER JOIN gp
                       ON transactions.id = gp.id
                       LEFT OUTER JOIN wages
                       ON transactions.id = wages.id
                       LEFT OUTER JOIN profit
                       ON transactions.id = profit.id
                       LEFT OUTER JOIN budgets
                       ON transactions.id = budgets.id
                       LEFT OUTER JOIN daily_stats
                       ON transactions.id = daily_stats.id
                       LEFT OUTER JOIN (SELECT t2.id, sum(CASE WHEN 
dt.till_name LIKE 'Main Bar%%' THEN dt.cash ELSE 0 END) as bar,
                                sum(CASE WHEN dt.till_name = 'Front Door 
Till' THEN dt.cash ELSE 0 END) as door_till,
                                (sum(CASE WHEN dt.till_name LIKE 'Main 
Bar%%' THEN dt.cash ELSE 0 END) +
                                sum(CASE WHEN dt.till_name = 'Front Door 
Till' THEN dt.cash ELSE 0 END)) as total,
                                sum(CASE WHEN dt.till_name = 'PR Cards' 
OR dt.till_name = 'Other Promo' THEN dt.cash ELSE 0 END) as promo
                            from transactions as t2, daily_takings as dt
                            WHERE t2.id = dt.id
                            GROUP BY t2.id
                            ) as dt
                        ON dt.id = transactions.id
                       WHERE transactions.for_venue = %s
                         AND week_num(for_date) between %s and %s
                    GROUP BY week_num(for_date)
                    ORDER BY week_num(for_date)"""

[Pypgsql-users] Dictionary Cursor?

[Jon-Pierre G. <jg...@se...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

I was curious as to whether or not anyone has attempted to implement
a cursor that returns a dictionary keyed from column names, similar
to the MySQLdb.DictCursor class?  I am not familiar enough with libpg
to implement it myself.

Thanks!

- --
_________________________________________________________

  Jon-Pierre Gentil               PGP: 0xA21BC30E
  jabber: jg...@se...    web: www.sebistar.net
  "If you think education is expensive, try ignorance."
_________________________________________________________
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iEYEAREDAAYFAkHlV2UACgkQOrVFmaIbww4CxgCeP6ZlzlMYT2m9ouGx5ne3Aj8r
0T0AoJ5mHYIPfvNmAylsfZQveqbtFsoN
=z8Qm
-----END PGP SIGNATURE-----

Re: [Pypgsql-users] problem with invalid characters

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

> i'm wondering why i get the following error witht he code below
> i'm guessing it's probably somethign very simple i'm goign wrong, most 
> likely to do with my new line escapes \
> if there is a better way of formatting my query to fix this i'm all ears.
consider using

query = """
... any formatting you want
"""

No \ needed.

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

[Pypgsql-users] problem with invalid characters

[Timothy S. <ti...@op...>]

i'm wondering why i get the following error witht he code below
i'm guessing it's probably somethign very simple i'm goign wrong, most 
likely to do with my new line escapes \
if there is a better way of formatting my query to fix this i'm all ears.
thanks in advance

cur.execute("CREATE OR REPLACE FUNCTION week_num ( date )\
  File "/usr/local/lib/python2.3/site-packages/pyPgSQL/PgSQL.py", line 
3072, in execute
    raise OperationalError, msg
libpq.OperationalError: ERROR:  syntax error at or near "20040701" at 
character


cur.execute("CREATE OR REPLACE FUNCTION week_num ( date )\
                    RETURNS integer AS '\
                    SELECT ($1 - (%s::date - extract(dow from 
%s::date)::integer + 1))/7;' \
                    LANGUAGE sql IMMUTABLE STRICT;\
                    \
                    CREATE OR REPLACE FUNCTION eow (integer) \
                    RETURNS date AS '\
                    SELECT for_date \
                    FROM transactions \
                    WHERE (transactions.for_date - (%s::date - 
extract(dow from %s::date)::integer + 1))/7 = $1\
                       AND EXTRACT(dow FROM transactions.for_date) = 0;'\
                    LANGUAGE sql IMMUTABLE STRICT;\
                    \
                    SELECT DISTINCT week_num(for_date),\
                       eow(week_num(for_date)),\
                       sum(dt.door_till) as door_till,\
                       sum(dt.bar) as bar,\
                       sum(dt.total) as income,\
                       sum(budget) as income_budget,\
                       sum(wages) as wages, sum(wages_budget) as 
wages_budget,\
                       sum(reads11pm) as reads11pm,\
                       sum(door_count) as door_count,\
                       sum(dt.promo) as promo,\
                       sum(gp) as gp,\
                       (sum(dt.total) / sum(door_count))::numeric (10,2) 
as head,\
                       sum(profit) as profit, sum(budget_profit) as 
budget_profit,\
                       (sum(budget_profit) / sum(dt.total))::numeric 
(10,2) as ror\
                    FROM transactions\
                       LEFT OUTER JOIN gp \
                       ON transactions.id = gp.id\
                       LEFT OUTER JOIN wages\
                       ON transactions.id = wages.id\
                       LEFT OUTER JOIN profit\
                       ON transactions.id = profit.id\
                       LEFT OUTER JOIN budgets\
                       ON transactions.id = budgets.id\
                       LEFT OUTER JOIN daily_stats\
                       ON transactions.id = daily_stats.id\
                       LEFT OUTER JOIN (SELECT t2.id, sum(CASE WHEN 
dt.till_name LIKE 'Main Bar%%' THEN dt.cash ELSE 0 END) as bar,\
                                sum(CASE WHEN dt.till_name = 'Front Door 
Till' THEN dt.cash ELSE 0 END) as door_till,\
                                (sum(CASE WHEN dt.till_name LIKE 'Main 
Bar%%' THEN dt.cash ELSE 0 END) +\
                                sum(CASE WHEN dt.till_name = 'Front Door 
Till' THEN dt.cash ELSE 0 END)) as total,\
                                sum(CASE WHEN dt.till_name = 'PR Cards' 
OR dt.till_name = 'Other Promo' THEN dt.cash ELSE 0 END) as promo\
                            from transactions as t2, daily_takings as dt\
                            WHERE t2.id = dt.id\
                            GROUP BY t2.id\
                            ) as dt \
                        ON dt.id = transactions.id\
                       WHERE transactions.for_venue = %s\
                         AND week_num(for_date) between %s and %s\
                    GROUP BY week_num(for_date)\
                    ORDER BY week_num(for_date)", (YearDate, YearDate, 
YearDate, YearDate,Venue, FromWeek, ToWeek))

[Pypgsql-users] odd problem

[Timothy S. <ti...@op...>]

 File "/usr/local/lib/python2.3/site-packages/pyPgSQL/PgSQL.py", line 
1598, in __rmul__
    return self.__mul__(self, other)
TypeError: __mul__() takes exactly 2 arguments (3 given)

anyone have an idea why i'm geting this error? at this point in my code 
i'm finished with pypgsql, yet it produces an error?!?

Re: [Pypgsql-users] error pypgsql "Ivalid format for PgVersion construction"

[Terry at i3 <te...@i3...>]

I may be wrong but I had a similar problem and it was fixed by a patch
on the sourceforge site.=20

Basically when you connect to postgres the postgres version is returned
to your app via pypgsql. the pypgsql code that handles this is in
PgVersion.c.  In RedHat versions of postgres the version string has an
RH appended to it (why??) and the pypgsql code does not handle that
eventuality therefore the connection fails.  The patch just makes the
acceptance of a valid version string looser.

Cheers

On Wed, 2004-12-29 at 08:28, Hector Miuler Malpica Gallegos wrote:

> >>> PgSQL.connect('xxxxxxx.com:5432:basexxxx:userxxx:passxxxxxx')
> Traceback (most recent call last):
>   File "<stdin>", line 1, in ?
>   File "/usr/lib/python2.3/site-packages/pyPgSQL/PgSQL.py", line 2211,
> in connect
>     return Connection(connInfo, client_encoding, unicode_results)
>   File "/usr/lib/python2.3/site-packages/pyPgSQL/PgSQL.py", line 2332,
> in __init__
>     raise DatabaseError, m
> libpq.DatabaseError: Ivalid format for PgVersion construction.
>=20
> :'( :'( :'( :'(
>=20
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> my server (no problem):
> basecsd=3D# SELECT pg_catalog.pg_client_encoding();
> pg_client_encoding
> --------------------
> SQL_ASCII
> (1 fila)
> basecsd=3D# SELECT version();
>                                                 version=20
> -----------------------------------------------------------------------=
--------------------------------
> PostgreSQL 7.4.6 on i386-pc-linux-gnu, compiled by GCC i386-linux-gcc
> (GCC) 3.3.4 (Debian 1:3.3.4-13)
> (1 fila)
>=20
>=20
> server external (error server):
> basecsd=3D> SELECT pg_catalog.pg_client_encoding();
> pg_client_encoding
> --------------------
> SQL_ASCII
> (1 fila)   =20
> basecsd=3D> select version();
>                                                    version=20
> -----------------------------------------------------------------------=
--------------------------------------
> PostgreSQL 7.3.6-RH on i686-pc-linux-gnu, compiled by GCC gcc (GCC)
> 3.2.3 20030502 (Red Hat Linux 3.2.3-20)
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
>=20
>=20
>=20
> El mi=C3=A9, 29-12-2004 a las 07:36 +0100, Gerhard Quell escribi=C3=B3:=
=20
>=20
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >=20
> > Use this:
> >=20
> > c1=3DPgSQL.connect('host:port:database:user:password:options:tty')
> >=20
> >=20
> > basic usage:
> > ~ PgSQL.connect(connect_string) -> connection  connect_string
> > ~ =3D'host:port:database:user:password:options:tty'
> > ~ All parts are optional. You may also pass the information in as
> > ~ keyword arguments with the following keywords: 'host', 'port',
> > ~ 'database', 'user', 'password', 'options', and 'tty'.  The port
> > ~ may also be passed in as part of the host keyword parameter,
> > ~ ie. host=3D'localhost:5432'. Other optional parameters are
> > ~ client_encoding and unicode_results. If unicode_results is true,
> > ~ all strings from the backend are returned as Unicode strings.
> > ~ client_encoding accepts the same parameters as the encode method
> > ~ of Unicode strings. If you also want to set a policy for encoding
> > ~ errors, set client_encoding to a tuple, like ("koi8-r", "replace")
> > ~ Note that you still must make sure that the PostgreSQL client is
> > ~ using the same encoding as set with the client_encoding parameter.
> > ~ This is typically done by issuing a "SET CLIENT_ENCODING TO ..."
> > ~ SQL statement immediately after creating the connection.
> >=20
> >=20
> >=20
> > Hector Miuler Malpica Gallegos wrote:
> > | Hello, I have problems with pypgsql, by means of psql I can be
> > | connected to a server with Postgresql=3D7.3.6, to a data base in wh=
ich I
> > | have access to everything.
> > | When attempt to connect to me with pypgsql I cannot, with others
> > | librerias for poststoneware if I can, this is the error message:
> > |
> > |
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
> > |
> > |>>>from pyPgSQL import PgSQL
> > |>>>c1=3DPgSQL.connect(user=3D"xxxx", password=3D"xxxxxxx",
> > |
> > | host=3D"serverxxx.xxx", database=3D"xxx")
> > | Traceback (most recent call last):
> > |   File "<stdin>", line 1, in ?
> > |   File "/usr/lib/python2.3/site-packages/pyPgSQL/PgSQL.py", line 22=
11,
> > | in connect
> > |     return Connection(connInfo, client_encoding, unicode_results)
> > |   File "/usr/lib/python2.3/site-packages/pyPgSQL/PgSQL.py", line 23=
31,
> > | in __init__
> > |     raise DatabaseError, m
> > | libpq.DatabaseError: Ivalid format for PgVersion construction.
> > |
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
> > |
> > |
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
> > |
> > |>>>from pyPgSQL import libpq
> > |>>>libpq.PQconnectdb('host=3Dserverxxx.xxx password=3Dxxxxxxx user=3D=
xxx
> > dbname=3Dxxxxxxx')
> > |
> > | Traceback (most recent call last):
> > |   File "<stdin>", line 1, in ?
> > | ValueError:
> >=20
> >=20
> > - --
> > - ------------------------------------------------------ skequell ---=
---
> > ~ Gerhard Quell                       Software & Knowledge Engineerin=
g
> > ~ Sch=C3=BCtzenweg 3      eMail:     gq...@sk...  Fon: 0731-26=
400651
> > ~ 89275 Elchingen    web  : http://www.skequell.de  Fax: 0731-2640065=
2
> > - --------------- pgp: 473EC53C  -  http://www.keyserver.net/en------=
---
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.3.92 (GNU/Linux)
> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> >=20
> > iD8DBQFB0lBAvHbZD0c+xTwRAhVRAKCp4IbsprzeUmH1I12qSS5PGuanCACgkKnt
> > 2C7sdhdayc5XzgwtTQD3Wew=3D
> > =3D6tSF
> > -----END PGP SIGNATURE-----
> >=20
> >=20
> > -------------------------------------------------------
> > SF email is sponsored by - The IT Product Guide
> > Read honest & candid reviews on hundreds of IT Products from real use=
rs.
> > Discover which products truly live up to the hype. Start reading now.=
=20
> > http://productguide.itmanagersjournal.com/
> > _______________________________________________
> > Pypgsql-users mailing list
> > Pyp...@li...
> > https://lists.sourceforge.net/lists/listinfo/pypgsql-users
>=20
> --=20
> Hector Miuler Malpica Gallegos <mi...@gm...>


________________________________________________________________________
Terry MacDonald MBA BEng
MIEE
Director and Principal
Consultant
i3 Technologies Ltd
Thunderbird - Reclaim
your inbox =20
Get Firefox affiliated
link =20

Re: [Pypgsql-users] error pypgsql "Ivalid format for PgVersion construction"

[Hector M. M. G. <mi...@gm...>]

>>> PgSQL.connect('xxxxxxx.com:5432:basexxxx:userxxx:passxxxxxx')
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "/usr/lib/python2.3/site-packages/pyPgSQL/PgSQL.py", line 2211,
in connect
    return Connection(connInfo, client_encoding, unicode_results)
  File "/usr/lib/python2.3/site-packages/pyPgSQL/PgSQL.py", line 2332,
in __init__
    raise DatabaseError, m
libpq.DatabaseError: Ivalid format for PgVersion construction.

:'( :'( :'( :'(


==============================================
my server (no problem):
basecsd=# SELECT pg_catalog.pg_client_encoding();
 pg_client_encoding
--------------------
 SQL_ASCII
(1 fila)
basecsd=# SELECT version();
                                                version 
-------------------------------------------------------------------------------------------------------
 PostgreSQL 7.4.6 on i386-pc-linux-gnu, compiled by GCC i386-linux-gcc
(GCC) 3.3.4 (Debian 1:3.3.4-13)
(1 fila)


server external (error server):
basecsd=> SELECT pg_catalog.pg_client_encoding();
 pg_client_encoding
--------------------
 SQL_ASCII
(1 fila)    
basecsd=> select version();
                                                   version 
-------------------------------------------------------------------------------------------------------------
 PostgreSQL 7.3.6-RH on i686-pc-linux-gnu, compiled by GCC gcc (GCC)
3.2.3 20030502 (Red Hat Linux 3.2.3-20)
==============================================




El mié, 29-12-2004 a las 07:36 +0100, Gerhard Quell escribió:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Use this:
> 
> c1=PgSQL.connect('host:port:database:user:password:options:tty')
> 
> 
> basic usage:
> ~ PgSQL.connect(connect_string) -> connection  connect_string
> ~ ='host:port:database:user:password:options:tty'
> ~ All parts are optional. You may also pass the information in as
> ~ keyword arguments with the following keywords: 'host', 'port',
> ~ 'database', 'user', 'password', 'options', and 'tty'.  The port
> ~ may also be passed in as part of the host keyword parameter,
> ~ ie. host='localhost:5432'. Other optional parameters are
> ~ client_encoding and unicode_results. If unicode_results is true,
> ~ all strings from the backend are returned as Unicode strings.
> ~ client_encoding accepts the same parameters as the encode method
> ~ of Unicode strings. If you also want to set a policy for encoding
> ~ errors, set client_encoding to a tuple, like ("koi8-r", "replace")
> ~ Note that you still must make sure that the PostgreSQL client is
> ~ using the same encoding as set with the client_encoding parameter.
> ~ This is typically done by issuing a "SET CLIENT_ENCODING TO ..."
> ~ SQL statement immediately after creating the connection.
> 
> 
> 
> Hector Miuler Malpica Gallegos wrote:
> | Hello, I have problems with pypgsql, by means of psql I can be
> | connected to a server with Postgresql=7.3.6, to a data base in which I
> | have access to everything.
> | When attempt to connect to me with pypgsql I cannot, with others
> | librerias for poststoneware if I can, this is the error message:
> |
> |
> ===========================================================================
> |
> |>>>from pyPgSQL import PgSQL
> |>>>c1=PgSQL.connect(user="xxxx", password="xxxxxxx",
> |
> | host="serverxxx.xxx", database="xxx")
> | Traceback (most recent call last):
> |   File "<stdin>", line 1, in ?
> |   File "/usr/lib/python2.3/site-packages/pyPgSQL/PgSQL.py", line 2211,
> | in connect
> |     return Connection(connInfo, client_encoding, unicode_results)
> |   File "/usr/lib/python2.3/site-packages/pyPgSQL/PgSQL.py", line 2331,
> | in __init__
> |     raise DatabaseError, m
> | libpq.DatabaseError: Ivalid format for PgVersion construction.
> |
> ===========================================================================
> |
> |
> ===========================================================================
> |
> |>>>from pyPgSQL import libpq
> |>>>libpq.PQconnectdb('host=serverxxx.xxx password=xxxxxxx user=xxx
> dbname=xxxxxxx')
> |
> | Traceback (most recent call last):
> |   File "<stdin>", line 1, in ?
> | ValueError:
> 
> 
> - --
> - ------------------------------------------------------ skequell ------
> ~ Gerhard Quell                       Software & Knowledge Engineering
> ~ Schützenweg 3      eMail:     gq...@sk...  Fon: 0731-26400651
> ~ 89275 Elchingen    web  : http://www.skequell.de  Fax: 0731-26400652
> - --------------- pgp: 473EC53C  -  http://www.keyserver.net/en---------
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.3.92 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQFB0lBAvHbZD0c+xTwRAhVRAKCp4IbsprzeUmH1I12qSS5PGuanCACgkKnt
> 2C7sdhdayc5XzgwtTQD3Wew=
> =6tSF
> -----END PGP SIGNATURE-----
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now. 
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Pypgsql-users mailing list
> Pyp...@li...
> https://lists.sourceforge.net/lists/listinfo/pypgsql-users

-- 
Hector Miuler Malpica Gallegos <mi...@gm...>

Re: [Pypgsql-users] error pypgsql "Ivalid format for PgVersion construction"

[Gerhard Q. <gq...@sk...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Use this:

c1=PgSQL.connect('host:port:database:user:password:options:tty')


basic usage:
~ PgSQL.connect(connect_string) -> connection  connect_string
~ ='host:port:database:user:password:options:tty'
~ All parts are optional. You may also pass the information in as
~ keyword arguments with the following keywords: 'host', 'port',
~ 'database', 'user', 'password', 'options', and 'tty'.  The port
~ may also be passed in as part of the host keyword parameter,
~ ie. host='localhost:5432'. Other optional parameters are
~ client_encoding and unicode_results. If unicode_results is true,
~ all strings from the backend are returned as Unicode strings.
~ client_encoding accepts the same parameters as the encode method
~ of Unicode strings. If you also want to set a policy for encoding
~ errors, set client_encoding to a tuple, like ("koi8-r", "replace")
~ Note that you still must make sure that the PostgreSQL client is
~ using the same encoding as set with the client_encoding parameter.
~ This is typically done by issuing a "SET CLIENT_ENCODING TO ..."
~ SQL statement immediately after creating the connection.



Hector Miuler Malpica Gallegos wrote:
| Hello, I have problems with pypgsql, by means of psql I can be
| connected to a server with Postgresql=7.3.6, to a data base in which I
| have access to everything.
| When attempt to connect to me with pypgsql I cannot, with others
| librerias for poststoneware if I can, this is the error message:
|
|
===========================================================================
|
|>>>from pyPgSQL import PgSQL
|>>>c1=PgSQL.connect(user="xxxx", password="xxxxxxx",
|
| host="serverxxx.xxx", database="xxx")
| Traceback (most recent call last):
|   File "<stdin>", line 1, in ?
|   File "/usr/lib/python2.3/site-packages/pyPgSQL/PgSQL.py", line 2211,
| in connect
|     return Connection(connInfo, client_encoding, unicode_results)
|   File "/usr/lib/python2.3/site-packages/pyPgSQL/PgSQL.py", line 2331,
| in __init__
|     raise DatabaseError, m
| libpq.DatabaseError: Ivalid format for PgVersion construction.
|
===========================================================================
|
|
===========================================================================
|
|>>>from pyPgSQL import libpq
|>>>libpq.PQconnectdb('host=serverxxx.xxx password=xxxxxxx user=xxx
dbname=xxxxxxx')
|
| Traceback (most recent call last):
|   File "<stdin>", line 1, in ?
| ValueError:


- --
- ------------------------------------------------------ skequell ------
~ Gerhard Quell                       Software & Knowledge Engineering
~ Schützenweg 3      eMail:     gq...@sk...  Fon: 0731-26400651
~ 89275 Elchingen    web  : http://www.skequell.de  Fax: 0731-26400652
- --------------- pgp: 473EC53C  -  http://www.keyserver.net/en---------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.3.92 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFB0lBAvHbZD0c+xTwRAhVRAKCp4IbsprzeUmH1I12qSS5PGuanCACgkKnt
2C7sdhdayc5XzgwtTQD3Wew=
=6tSF
-----END PGP SIGNATURE-----

[Pypgsql-users] error pypgsql "Ivalid format for PgVersion construction"

[Hector M. M. G. <mi...@gm...>]

Hello, I have problems with pypgsql, by means of psql I can be
connected to a server with Postgresql=7.3.6, to a data base in which I
have access to everything.
When attempt to connect to me with pypgsql I cannot, with others
librerias for poststoneware if I can, this is the error message:

===========================================================================
>>> from pyPgSQL import PgSQL
>>> c1=PgSQL.connect(user="xxxx", password="xxxxxxx",
host="serverxxx.xxx", database="xxx")
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "/usr/lib/python2.3/site-packages/pyPgSQL/PgSQL.py", line 2211,
in connect
    return Connection(connInfo, client_encoding, unicode_results)
  File "/usr/lib/python2.3/site-packages/pyPgSQL/PgSQL.py", line 2331,
in __init__
    raise DatabaseError, m
libpq.DatabaseError: Ivalid format for PgVersion construction.
===========================================================================

===========================================================================
>>> from pyPgSQL import libpq
>>> libpq.PQconnectdb('host=serverxxx.xxx password=xxxxxxx user=xxx dbname=xxxxxxx')
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
ValueError: 
-- 
Hector Miuler Malpica Gallegos <mi...@gm...>

[Pypgsql-users] Ivalid format for PgVersion construction :'(

[Hector M. M. G. <mi...@gm...>]

Hello, I have problems to connect to me with an external server: 

===========================================================
>>> cn1=PgSQL.connect(user='xxx', password='xxxxxxxx',
host='xxxxxxx.xxx', database='basecsd')
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "/usr/lib/python2.3/site-packages/pyPgSQL/PgSQL.py", line 2211,
in connect
    return Connection(connInfo, client_encoding, unicode_results)
  File "/usr/lib/python2.3/site-packages/pyPgSQL/PgSQL.py", line 2331,
in __init__
    raise DatabaseError, m
libpq.DatabaseError: Ivalid format for PgVersion construction.
===========================================================


but with pgsql I do not have problems, that can be bad?
===========================================================
miuler@miuler:~$ psql -h xxxxxxxxx.xxx -U xxx basecsd
Contraseña:
Bienvenido a psql 7.4.6, el terminal interactivo de PostgreSQL.

Digite:  \copyright para ver los términos de distribución
         \h para obtener ayuda sobre comandos SQL
         \? para obtener ayuda sobre comandos internos
         \g o termine con punto y coma (;) para ejecutar consulta
         \q para salir
basecsd=>
===========================================================


server:
PostgreSQL            = 7.3.6

host:
python2.3               = 2.3.4-18
python2.3-pgsql     = 2.4.0-5
libpq3                     = 7.4.6-5

Re: [Pypgsql-users] compile on windows

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

jo...@cy... wrote:
> Has anyone successfully compiled Postgresql 8RC1 with python 2.4 on
> windows?  I've tried several time with both VC7 (.net) and mingw but
> have not been able to get it to compile

Does this help?

http://ghaering.de:9080/pypgsql/

You need the PostgreSQL client libraries in addition to this, though. I 
recommend installing the latest, PgAdmin III, which includes 
(SSL-enabled) client libraries for the latest PostgreSQL win32 build.

-- Gerhard

[Pypgsql-users] compile on windows

[<jo...@cy...>]

Has anyone successfully compiled Postgresql 8RC1 with python 2.4 on
windows?  I've tried several time with both VC7 (.net) and mingw but
have not been able to get it to compile

Jose

[Pypgsql-users] query lines

[Timothy S. <ti...@op...>]

sorry i know this must sound simple, but i'd like to implement some kind 
of formatting in my queries, yet pgsql errors on a new line.

[Pypgsql-users] changing autocommit

[<le...@as...>]

Hello guyz, 
    I am having a trouble with autocommit, the problem is: 
    I want that autocommit be alway on. Then i did a function called 
    atomic_start, that turn autocommit off and make the next commands a 
    transaction, so when i call atmic_commit, it commits,
    self.connection.commit. But i see that i cant change autocommit after i
    have activate a cursor, see: 

    AttributeError: Can't change autocommit when a cursor is active.

    Any suggestion?

Cheers, 

Breno Leitao
http://lcr.icmc.usp.br/~leitao
-- 
Async Open Source
(16) 3361 2331
São Carlos, SP
Brasil

Code: 
    def atomic_start(self):
        self.connection.autocommit = 0
        self.run_query(query)

    def atomic_commit(self): 
        self.connection.commit()
        self.connection.autocommit = 1