[BUGS] [postgres] dblink für Postgres

2005-06-17 Thread Carsten Sommer
Hallo,

ich habe bis jetzt Sachdaten und Kataloge in getrennten Datenbanken
gehalten. Eine Tcl/Tk Anwendung bringt beides zusammen. Fr Webausknfte
brauche ich aber komplexe SQL Abfragen, die dann die OBJID der Kataloge
auflosen.
Es gibt nun die Mglichkeit die Tabellen der kataloge in die Sachdatenbank
zu integrieren.
Ich habe krzlich von der Mglichkeit contrib/dblink kann mir aber darunter
nichts genaueres vorstellen -- irgendwie musz tmplate1 verndert werden.

Wie kann ich mein Problem lsen kann jemand helfen?

-- 
Geschenkt: 3 Monate GMX ProMail gratis + 3 Ausgaben stern gratis
++ Jetzt anmelden  testen ++ http://www.gmx.net/de/go/promail ++


Wenn Sie Ihr Abonnement fuer diese Gruppe kuendigen moechten, senden 
Sie eine E-Mail an:
[EMAIL PROTECTED]

 
Yahoo! Groups Links

* Besuchen Sie Ihre Group im Web unter:
http://de.groups.yahoo.com/group/postgres/

* Um sich von der Group abzumelden, senden Sie eine Mail an:
[EMAIL PROTECTED]

* Mit der Nutzung von Yahoo! Groups akzeptieren Sie unsere:
http://de.docs.yahoo.com/info/utos.html
 



---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
  joining column's datatypes do not match


[BUGS] PostgreSQL 8.0.3 : initdb fails with the time zone value WAT0 on HP-Unix platforms

2005-06-17 Thread Kathir Velu



Hello All,

 PostgreSQL-8.0.3 doesnot work 
with time zone value WAT0 ( for West Africa Time ). 
HP Unix 11.23 PA and IPF servers set thetime 
zone valuefor West Africa Time as "WAT0" in it's "/etc/TIMEZONE" 
file.

When we try to initialize the database directories 
using initdb command, we get the following error,

$ initdb -D /var/opt/iexpress/postgresqlThe 
files belonging to this database system will be owned by user 
"postgres".This user must also own the server process.

The database cluster will be initialized with 
locale C.

fixing permissions on existing directory 
/var/opt/iexpress/postgresql... okcreating directory 
/var/opt/iexpress/postgresql/base... okcreating directory 
/var/opt/iexpress/postgresql/global... okcreating directory 
/var/opt/iexpress/postgresql/pg_xlog... okcreating directory 
/var/opt/iexpress/postgresql/pg_clog... okselecting default 
max_connections... 10selecting default shared_buffers... 50creating 
configuration files... okcreating template1 database in 
/var/opt/iexpress/postgresql/base/1... FATAL: invalid value for parameter 
"timezone": "WAT0"

initdb: failed

 When we changed theserver 
timezone value to "WAT-01:00" in TZ environment variable 
as specified in http://www.postgresql.org/docs/7.4/static/datetime-keywords.html, 
it worked well. 

However it has to be work for time zone value 
"WAT0", generated by server for West Africa Time.
So possibly this could be the bug with the 
postgresql.Can you please provide a patch to fx this issue in PostgreSQL 
source ?

thanks,Kathir.

		Yahoo! Mail Mobile 
Take Yahoo! Mail with you! Check email on your mobile phone.

Re: [BUGS] PostgreSQL 8.0.3 : initdb fails with the time zone value WAT0 on HP-Unix platforms

2005-06-17 Thread Tom Lane
Kathir Velu [EMAIL PROTECTED] writes:
 PostgreSQL-8.0.3 doesnot work with time zone value WAT0 ( for West Africa 
 Time ).  

Hmm, is there someplace where that is actually used?  The zic timezone
database says that WAT generally means GMT+1 not GMT.

 So possibly this could be the bug with the postgresql. Can you please provide 
 a patch to fx this issue in PostgreSQL source ?

We are not in the business of thinking that we know better than the
people who maintain the timezone database.  I'd suggest taking it up
with the timezone list ([EMAIL PROTECTED]) if you think this is
correct and not an error on HP's part.

regards, tom lane

---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])


[BUGS] plpython regression test leaves /tmp/plpython file

2005-06-17 Thread Kris Jurka

The plpython regression test leaves a file /tmp/plpython around after the 
tests have completed running.  This causes a subsequent failure if the 
tests are run with another user running the database because a permission 
denied error will be returned when trying to write the /tmp/plpython file.

Kris Jurka

---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]


[BUGS] BUG #1720: placeholders do not work with timestamp prefix

2005-06-17 Thread Wellie Chao

The following bug has been logged online:

Bug reference:  1720
Logged by:  Wellie Chao
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 8.0.0
Operating system:   Linux (with kernel 2.4.18)
Description:placeholders do not work with timestamp prefix
Details: 

I am using DBI 1.48 and DBD::Pg 1.42 (the programming language is obviously
Perl) to connect to PostgreSQL 8.0.0. The following statements cause
problems:

2005-06-17 16:21:41 EDT LOG:  statement: select * from reservation_tbl where
room_id = $1 and (start_dt, end_dt) overlaps (timestamp $2, timestamp $3)
2005-06-17 16:21:41 EDT ERROR:  syntax error at or near $2 at character
93
2005-06-17 16:21:41 EDT LOG:  statement: insert into reservation_tbl
(room_id, account_id, start_dt, end_dt, note) values ($1, $2, timestamp $3,
timestamp $4, $5)
2005-06-17 16:21:41 EDT ERROR:  syntax error at or near $3 at character
101

I think it is something to do with the timestamp keyword interacting badly
with placeholders.

---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]


Re: [BUGS] BUG #1720: placeholders do not work with timestamp prefix

2005-06-17 Thread Tom Lane
Wellie Chao [EMAIL PROTECTED] writes:
 I am using DBI 1.48 and DBD::Pg 1.42 (the programming language is obviously
 Perl) to connect to PostgreSQL 8.0.0. The following statements cause
 problems:

 2005-06-17 16:21:41 EDT LOG:  statement: select * from reservation_tbl where
 room_id = $1 and (start_dt, end_dt) overlaps (timestamp $2, timestamp $3)
 2005-06-17 16:21:41 EDT ERROR:  syntax error at or near $2 at character
 93

The above is not valid SQL --- the notation timestamp x is only legal
when x is a simple string literal.  I think you need to complain to the
DBI or DBD::Pg folk, if their code is generating this query.

regards, tom lane

---(end of broadcast)---
TIP 6: Have you searched our list archives?

   http://archives.postgresql.org