Re: [BUGS] pg_dump case folding bug

2004-11-13 Thread Russell Smith
On Sat, 13 Nov 2004 04:05 pm, Tom Lane wrote: > Russell Smith <[EMAIL PROTECTED]> writes: > > pg_dump does not fold case, and quote table and schema names correctly. > > This is not a bug; it is a behavior we deliberately adopted years ago, > after unsuccessful experiments with behavior like what

[BUGS] Bug in Installation

2004-11-13 Thread Prabhu Ram Prasath V
Hi,   I get an installation error which says ...\pgoledb.dll failed to register.  My OS is Windows 2000 SP 4 System.   Please give me a resolution.   Regards, Prabhu Ram

[BUGS] Bug no tipo de dados "text" do PostgreSQL 8.0-beta1

2004-11-13 Thread Fabio
Olá, Estou desenvolvendo um sistema de controle de estoque em Java com a Base de Dados PostgreSQL 8.0-beta 1. Utilizei os Bancos Access e SQL Server e o Java consegue ler tipos de dados do tipo text mas o PostgreSQL não permite,ele consegue ler somente números inteiros. No PostgreSQL versão 7

[BUGS] Error in sql sintax

2004-11-13 Thread Abaco informática s . a .
this sentence is accepted by postgresql sintax analizer but we think that's incorrect:   select * from table T where T.field = table.field_1   it take the result as an inner join between 'T' and 'table' which not exist ... just exists 'T'.   this occurs in linux versions and windows ve

[BUGS] help in installation

2004-11-13 Thread Estevan Rech
Hi!   I’m still with the problem in installation of postgre; "failed to create process for initdb". I create two users with a greate permission in Windows2003.   Can you help me, like a screen with the users creates or other thing?   So, tanks.     Estevan Rech Software Developer

Re: [BUGS] Error in sql sintax

2004-11-13 Thread Stephan Szabo
On Tue, 9 Nov 2004, [iso-8859-1] Abaco informática s.a. wrote: > this sentence is accepted by postgresql sintax analizer but we think > that's incorrect: > > select * from table T where T.field = table.field_1 > > it take the result as an inner join between 'T' and 'table' which not > exist ... j

[BUGS] PostgreSQL 8 Installed on Windows

2004-11-13 Thread Stefano Tazzi
Hi, I've installed successfully PostgreSQL on Windows XP. PostgreSQL is installed on user postgresql, with non administrative permission. I try to use "createdb" to create a mydb but I'm not able to archive the operation with success. Error message (on a DOS prompt window) is the following: C:

[BUGS] wrong thousand/group separator with to_char on certain locales...

2004-11-13 Thread Netto
Hey all,... I've faced a "bogus" situation in postgreSQL while using "to_char" function with locale resources that was described before at http://archives.postgresql.org/pgsql-bugs/2003-05/msg00065.php, and I was able to identify what the real problem is...

[BUGS] PostgresQL 8 beta 4 bugs

2004-11-13 Thread Kristian Jörg
Hello, I have found two bugs relating to the Windows port, i.e installing on Windows XP Professional. 1) Trying to install with finnish locale does not work, the service starts but installation procedure halts in the end when trying to install and activate "procedural languages" if I remember c

[BUGS] Unable to run PostgreSQL 8 beta 3 on Windows XP Home

2004-11-13 Thread Ganesh and Sashi Prasad
Hi, I downloaded PostgreSQL 8 beta 3 for my PC running Windows XP Home. Before installing PostgreSQL, I first created a normal user called "postgres" with no administrator privileges. Then, when setting up the software, I specified this user to run under. Unfortunately, I could never run postmast

Re: [BUGS] SELECT FOR UPDATE and LIMIT 1 behave oddly

2004-11-13 Thread andrea suisani
hi! Josh Berkus wrote: > Bruce, > [snip] > > > Well, limit+for update can be useful under some circumstances, as long as you > understand its limitations.We found a workaround. i'm sorry for the curiosity but could you share, if it's possible, this workaround? ;) andrea

Re: [BUGS] SELECT FOR UPDATE and LIMIT 1 behave oddly

2004-11-13 Thread Andrea Suisani
tnks for the hint ;) I'll try something similar here. Andrea Josh Berkus wrote: Andrea, i'm sorry for the curiosity but could you share, if it's possible, this workaround? ;) (if it's not the one you describe at the beginning thread e.g. don't use LIMIT 1) Well, we actually roped in the pg_l