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

[Pypgsql-users] binary mode

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

is there a version of pypgsql that support pg 8's binary mode? i can 
cvsup and compile, doesn't need to be packaged

Re: [Pypgsql-users] query size

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

On Fri, Feb 18, 2005 at 04:52:26PM +1000, Timothy Smith wrote:
> is there anyway i can calculate how much data is going ot be sent in a=20
> query. i know it will depend on the data etc, but there must be certain=
=20
> over head per row etc i need to account for. it'll will help me=20
> determine how much traffic and bandwidth i need to account for and how=20
> many users i can load per connection.

The PostgreSQL frontend-backend protocol is documented here:
http://www.postgresql.org/docs/current/static/protocol.html

HTH,

-- Gerhard

[Pypgsql-users] query size

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

is there anyway i can calculate how much data is going ot be sent in a 
query. i know it will depend on the data etc, but there must be certain 
over head per row etc i need to account for. it'll will help me 
determine how much traffic and bandwidth i need to account for and how 
many users i can load per connection

[Pypgsql-users] Options for connect

[J.Pierre P. <pt...@fr...>]

does anybody know values for option in connect function ?
Help is missing for this feature in the doc.

Thanks for advance
Jean-Pierre

Re: [Pypgsql-users] tables with small letters?

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

On Wednesday 09 February 2005 01:40 am, Mican Bican wrote:

> Thanks Ben .. this was the problem! So I think I is it better to change
> all to lower case in the db structure. But I dont understand why this
> is so?? PgAdminIII generate a sql code, for example create table
> "Table" ... so thats mean when i create table manually with create
> table Table, and write a select statement like this: select * from
> Table without " than its works?? Hmm thanks for your help...
> (can I turn off the function in pgAdminIII to add the " in the create
> statements?)

pgAdminIII does precisely as you tell it to.  It will enclose an=20
identifier in quotation marks if you specify any capital letters in the=20
name.  Thus, afterwords, you must specifically quote the name back to it=20
identically otherwise it does not see it correctly.

So the moral of the story is, never use capital letters.  Or stop using=20
pgAdminIII.  :) =20

=2D-=20
_________________________________________________________

  Jon-Pierre Gentil               PGP: 0xA21BC30E
  jabber: jg...@se...    web: www.sebistar.net
  "If you think education is expensive, try ignorance."
_________________________________________________________=20

Re: [Pypgsql-users] tables with small letters?

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

> Thanks Ben .. this was the problem! So I think I is it better to change 
> all to lower case in the db structure. But I dont understand why this is 
> so??
Read my previous post.

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

Re: [Pypgsql-users] tables with small letters?

[Mican B. <mi...@gm...>]

Ben Scherrey schrieb:

> Unfortunately table names that aren't pure lower-case are a bit 
> annoying. I converted an app from Access to Postgres and changing the 
> code for all the table names wasn't an option. Try changing your 
> select statement to: 'select * from "Farbton"' and see if that doesn't 
> work. Everywhere you reference a table name you will have to enclose 
> it in "". Its up to you to decide which is the bigger pain in the butt 
> to deal with, quoting table names or changing them to lower case in 
> the db structure.
>
>    good luck,


Thanks Ben .. this was the problem! So I think I is it better to change 
all to lower case in the db structure. But I dont understand why this is 
so?? PgAdminIII generate a sql code, for example create table "Table" 
... so thats mean when i create table manually with create table Table, 
and write a select statement like this: select * from Table without " 
than its works?? Hmm thanks for your help...
(can I turn off the function in pgAdminIII to add the " in the create 
statements?)

--Muhlis

Re: [Pypgsql-users] tables with small letters?

[Ben S. <sch...@pr...>]

Unfortunately table names that aren't pure lower-case are a bit 
annoying. I converted an app from Access to Postgres and changing the 
code for all the table names wasn't an option. Try changing your select 
statement to: 'select * from "Farbton"' and see if that doesn't work. 
Everywhere you reference a table name you will have to enclose it in "". 
Its up to you to decide which is the bigger pain in the butt to deal 
with, quoting table names or changing them to lower case in the db 
structure.

    good luck,

       Ben Scherrey

Mican Bican wrote:

> Gerhard Häring schrieb:
>
>> Mican Bican wrote:
>>
>>> Hello,
>>>
>>> I write a test python file to connect my postgresql database. My 
>>> table called Testtabelle. Python always bring an error... "a 
>>> relation called testtabelle not exists" or so.. So I try to change 
>>> the tablename from Testtabelle to testtabelle... uups and it 
>>> works..?? Is this possible that pypgsql only allows tablenames with 
>>> small letters????
>>
>>
>>
>> pyPgSQL has nothing to do with it. Probably the table was created 
>> with something like:
>>
>> create table "Testtabelle"
>>
>> and then, case does matter I believe. At least I've seen something 
>> like this recently in Oracle.
>>
>> -- Gerhard
>>
>>
>> -------------------------------------------------------
>> 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>> _______________________________________________
>> Pypgsql-users mailing list
>> Pyp...@li...
>> https://lists.sourceforge.net/lists/listinfo/pypgsql-users
>>
> I  create the tabel with pgadmin, I run the programm with IDLE .. I 
> dont know what is the problem.. all tools are the last version..
> i add one screenshot from the error.. probably it is a problem from 
> python??
>
> --Muhlis
>
> ------------------------------------------------------------------------
>

Re: [Pypgsql-users] tables with small letters?

[Mican B. <mi...@gm...>]

Gerhard Häring schrieb:

> Mican Bican wrote:
>
>> Hello,
>>
>> I write a test python file to connect my postgresql database. My 
>> table called Testtabelle. Python always bring an error... "a relation 
>> called testtabelle not exists" or so.. So I try to change the 
>> tablename from Testtabelle to testtabelle... uups and it works..?? Is 
>> this possible that pypgsql only allows tablenames with small letters????
>
>
> pyPgSQL has nothing to do with it. Probably the table was created with 
> something like:
>
> create table "Testtabelle"
>
> and then, case does matter I believe. At least I've seen something 
> like this recently in Oracle.
>
> -- Gerhard
>
>
> -------------------------------------------------------
> 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Pypgsql-users mailing list
> Pyp...@li...
> https://lists.sourceforge.net/lists/listinfo/pypgsql-users
>
I  create the tabel with pgadmin, I run the programm with IDLE .. I dont 
know what is the problem.. all tools are the last version..
i add one screenshot from the error.. probably it is a problem from python??

--Muhlis

Re: [Pypgsql-users] tables with small letters?

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

You should better post on a PostgreSQL-specific list such as
pgsql-general.

> I write a test python file to connect my postgresql database. My table 
> called Testtabelle. Python always bring an error... "a relation called 
> testtabelle not exists" or so.. So I try to change the tablename from 
> Testtabelle to testtabelle... uups and it works..?? Is this possible 
> that pypgsql only allows tablenames with small letters????

The SQL standard says that table names must be case
insensitive. It suggests to fold all names to UPPERCASE.
PostgreSQL acts by the standard and uses table names case
insensitive. However, it folds all names to *lower*case (I
tend to agree that is more readable). So, Testtable,
TESTtable, tesTTable are all testtable as far as PostgreSQL is
concerned.

You *can* make PostgreSQL be case sensitive with table names,
however: just use quotes ("") around the names -- always !

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

Re: [Pypgsql-users] tables with small letters?

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

Mican Bican wrote:
> Hello,
> 
> I write a test python file to connect my postgresql database. My table 
> called Testtabelle. Python always bring an error... "a relation called 
> testtabelle not exists" or so.. So I try to change the tablename from 
> Testtabelle to testtabelle... uups and it works..?? Is this possible 
> that pypgsql only allows tablenames with small letters????

pyPgSQL has nothing to do with it. Probably the table was created with 
something like:

create table "Testtabelle"

and then, case does matter I believe. At least I've seen something like 
this recently in Oracle.

-- Gerhard

[Pypgsql-users] tabelnames only with small letters allowed?

[Mican B. <mi...@gm...>]

Hello,

I write a test python file to connect my postgresql database. My table
called Testtabelle. Python always bring an error... "a relation called
testtabelle not exists" or so.. So I try to change the tablename from
Testtabelle to testtabelle... uups and it works..?? Is this possible
that pypgsql only allows tablenames with small letters????

thank you

Muhlis

[Pypgsql-users] tables with small letters?

[Mican B. <mi...@gm...>]

Hello,

I write a test python file to connect my postgresql database. My table 
called Testtabelle. Python always bring an error... "a relation called 
testtabelle not exists" or so.. So I try to change the tablename from 
Testtabelle to testtabelle... uups and it works..?? Is this possible 
that pypgsql only allows tablenames with small letters????

thank you

Muhlis

Re: [Pypgsql-users] Import error using pyPgSQL

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

On Mon, Feb 07, 2005 at 02:10:58PM -0700, Kincaid, Larry wrote:
> Hi Folks-
> I know there's probably an easy answer to this question but it's not
> coming to me so I thought I'd ask for help.  I think I've successfully
> built and installed the pyPgSQL module and I know for sure libpq is
> installed and working because I've used it in a small C program
> interfacing with my PostgreSQL database.  However, in my Python code,
> the line "from pyPgSQL import PgSQL" causes an error "ImportError:
> /usr/lib/python2.3/site-packages/pyPgSQL/libpq/libpqmodule.so: undefined
> symbol: lo_export".   [...]

I wonder if it's possible to compile PostgreSQL without Large Object
support and wether Fedora has done so.

-- Gerhard

[Pypgsql-users] Import error using pyPgSQL

[Kincaid, L. <lw...@sa...>]

Hi Folks-
I know there's probably an easy answer to this question but it's not
coming to me so I thought I'd ask for help.  I think I've successfully
built and installed the pyPgSQL module and I know for sure libpq is
installed and working because I've used it in a small C program
interfacing with my PostgreSQL database.  However, in my Python code,
the line "from pyPgSQL import PgSQL" causes an error "ImportError:
/usr/lib/python2.3/site-packages/pyPgSQL/libpq/libpqmodule.so: undefined
symbol: lo_export". =20

Any ideas?  This is on a PC running Linux Fedora Core 2, Python 2.3 and
PostgreSQL 7.3.4.  I can always call the C program from Python and that
works fairly well but at this point I'm exploring options.  Plus, to be
honest, it's a little annoying that one way works and the other doesn't
so now I'm curious as to why.  Any help, thoughts or suggestions would
be greatly welcomed.

- larry

Larry Kincaid
Sandia National Laboratories
lw...@sa...
(505) 845-0125

[Pypgsql-users] Maintenance

[Rod M. <rma...@in...>]

I have seen some posts hinting at the possibility that pypgsql is no =
longer being maintained. Does anyone know for sure?

Rod MacNeil


=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
NOTE: This e-mail message is intended only for the named recipient(s) =
above and may contain information that is privileged, confidential =
and/or exempt from disclosure under applicable law. If you have received =
this message in error, or are not the named recipient(s), please =
immediately notify the sender and delete this e-mail 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

Re: [Pypgsql-users] funny behavour

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

> theres kind of nothing more to it :\

Python version
PG version
pyPgSQL version

- example python code ...
- contained PostgreSQL schema ...
- test data ...

... needed to reproduce the error

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

Re: [Pypgsql-users] funny behavour

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

Karsten Hilbert wrote:

>>126752.95 9841
>><type 'instance'> <type 'PgInt8'>
>>
>>the above values can'ts be / by. it returns a none type. but if i just 
>>int() the last value it works like a charm
>>    
>>
>You will have to post more information to find help.
>
>Karsten
>  
>
theres kind of nothing more to it :\
the above values were part of a list, i was doing  x = Totals[4] / 
Totals[9] the above out put is the result of
print Totals[4], Totals[9]
print type(Totals[4]), type(Totals[9])

Re: [Pypgsql-users] funny behavour

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

> 126752.95 9841
> <type 'instance'> <type 'PgInt8'>
> 
> the above values can'ts be / by. it returns a none type. but if i just 
> int() the last value it works like a charm
You will have to post more information to find help.

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

[Pypgsql-users] python 2.4 on WinXP: precisision lost with float values

[Christoph B. <cgb...@gm...>]

I used the inoffical compiled pypgsql version for Python 2.4, made 
available by Gerhard Häring.
In the database (PgSQL Version 8.0 as well as 7.4.3) I do have a column 
with type float8 and values like 2.3.

This worked and still worked and still works fine on Windows with Python 
2.3.
With Python 2.4 however, with pypgsql, with cursor.execute() and then 
cursor.fetchall() for example, I got only  a value of 2.0 while 2.3 is 
still in the database.
With every value in this column I just got a zero at the right side of 
the decimal point.
After switching back to python 2.3 everything works fine again. 
It seems there is a bug in the newer version of pypgsql.

Regards
Christoph Becker

[Pypgsql-users] funny behavour

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

126752.95 9841
<type 'instance'> <type 'PgInt8'>

the above values can'ts be / by. it returns a none type. but if i just 
int() the last value it works like a charm

[Pypgsql-users] instruccion para que me liste el nombre de las columnas de la tabla

[Milton i. <min...@gm...>]

pero el modelo no de los datos, necesito que me lo almacena en una
lista o diccionario

ejemplo:
nombre_usuario | apellido_usuario |
=3D=3D=3D=3D=3D=3D=3D=3D=3D  |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D |
fernando             | barra                   |

lo que quiero me entregue en un arreglo es nombre_usuario y apellido_usuari=
o
--=20
Milton Inostroza Aguilera
Secretario Academico
Ingenieria Civil en Computaci=F3n e Inform=E1tica
Organizador
6to. Encuentro Nacional de Linux
Desarrollador de RemuneX (sistema amparado bajo GPL)
Integrante de GULIqq
Universidad Arturo Prat
Iquique - Chile

Re: [Pypgsql-users] pypgsql and postgresql 8

[Michael H. <Mi...@Hi...>]

Chris Schleiermacher wrote:
> 
> 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. 

You  didn't say what platform you're primarily interested in. If Win32, 
I've had good success using these binaries from Gerhard Häring:

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

Gerhard is a lead developer on pypgsql.

I'm not using it on a *nix platform right now so I can't say about that.

Michael

Re: [Pypgsql-users] pypgsql and postgresql 8

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

> Opps sorry for jumping to conclusions, I was really hoping that this was in
> fact not the case, I think that is a great API
Well, it is written to the API specs set forth by the Python
DB team. Which are lacking here and there, too, BTW.

One thing that would be really good to know is whether and
when pyPgSQL will support the out-of-band parameter passing.
Or does it do so already ? (Not that I know.)

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...>]

Opps sorry for jumping to conclusions, I was really hoping that this was =
in
fact not the case, I think that is a great API and I would hate to see =
it go
away especially now that postgresql 8 is officially out
Jose

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


> If I've read this correctly the implication is that PyPgSQL is not=20
> 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
--=20
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting =
Tool
for open source databases. Create drag-&-drop reports. Save time by over
75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download =
a
FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Pypgsql-users mailing list
Pyp...@li...
https://lists.sourceforge.net/lists/listinfo/pypgsql-users