Re: [BUGS] BUG #1581: Problem with capitalised DB names...

2005-04-11 Thread Marcus v. Scotti
Hi Bruno, Oops, I've overlooked that passage. Thanks for your help and sorry for wasting your time. Best Ragards Marcus On Apr 11, 2005 6:18 PM, Bruno Wolff III <[EMAIL PROTECTED]> wrote: > On Mon, Apr 11, 2005 at 09:37:08 +0100, > "Marcus v. Scotti" <[EMAIL PROTECTED]> wrote: > > > > Thank

Re: [BUGS] BUG #1582: boolean DEFAULT TRUE results in FALSE for NULL values

2005-04-11 Thread Eric McGough
I made a mistake. Postgres does put a NULL in the field (albiet I would still like to see postgres/COPY change the NULL to TRUE if DEFAULT is set to true), it appears pgAdmin III version 1.2.0 is the one displaying a boolean NULL as FALSE (as opposed to NULL). Sorry for not testing a little bit m

Re: [BUGS] BUG #1581: Problem with capitalised DB names...

2005-04-11 Thread Marcus v. Scotti
Hi Bruno, Thanks... (maybe include this in the manuals, I couldn't find this information...) Best Regards Marcus On Apr 10, 2005 11:23 PM, Bruno Wolff III <[EMAIL PROTECTED]> wrote: > On Tue, Apr 05, 2005 at 18:09:25 +0100, > "Marcus v. Scotti" <[EMAIL PROTECTED]> wrote: > > > > Description

Re: [BUGS] BUG #1581: Problem with capitalised DB names...

2005-04-11 Thread Bruno Wolff III
On Mon, Apr 11, 2005 at 09:37:08 +0100, "Marcus v. Scotti" <[EMAIL PROTECTED]> wrote: > > Thanks... (maybe include this in the manuals, I couldn't find this > information...) It is: http://developer.postgresql.org/docs/postgres/sql-syntax.html#SQL-SYNTAX-IDENTIFIERS ---

Re: [BUGS] BUG #1592: "with hold" cursor problem

2005-04-11 Thread Tom Lane
Alvaro Herrera <[EMAIL PROTECTED]> writes: > One further question is if it's right for the holdable portal to fire > trigger at transaction commit. ISTM the non-surprising answer would be > for them to fire at FETCH time. (But of course this is hard to > implement, since at that time we don't hav

Re: [BUGS] BUG #1592: "with hold" cursor problem

2005-04-11 Thread Alvaro Herrera
On Mon, Apr 11, 2005 at 11:49:22AM -0400, Tom Lane wrote: > The problem here is that CommitTransaction shuts down the trigger > manager before shutting down portals, so of course trigger.c barfs > when the SQL function wants it to check for queued triggers. > > There seems to be a rather fundamen

Re: [BUGS] BUG #1592: "with hold" cursor problem

2005-04-11 Thread Tom Lane
Andrew - Supernews <[EMAIL PROTECTED]> writes: > test=# create function crashme() returns text as 'select timeofday()' > test-# language sql stable; > CREATE FUNCTION > test=# begin; > BEGIN > test=# declare t cursor with hold for select crashme() as x from pg_class; > DECLARE CURSOR > test=# com

Re: [BUGS] BUG #1547: CREATE TYPE AS error

2005-04-11 Thread Michael Fuhr
On Mon, Apr 11, 2005 at 10:54:43AM -0400, Tom Lane wrote: > Michael Fuhr <[EMAIL PROTECTED]> writes: > > In the following message, the OP says that CREATE TYPE works if he > > installs PostgreSQL as a service but it doesn't work if he installs > > PostgreSQL as a program (can anybody think of why t

Re: [BUGS] BUG #1592: "with hold" cursor problem

2005-04-11 Thread Andrew - Supernews
On 2005-04-10, Tom Lane <[EMAIL PROTECTED]> wrote: > "Gabor Berenyi" <[EMAIL PROTECTED]> writes: >> begin; >> declare t cursor with hold for select function() as x from R; >> commit; > >> Documentation says that the rows represented by a held cursor are copied >> into a temporary file or memory a

Re: [BUGS] BUG #1547: CREATE TYPE AS error

2005-04-11 Thread Tom Lane
Michael Fuhr <[EMAIL PROTECTED]> writes: > In the following message, the OP says that CREATE TYPE works if he > installs PostgreSQL as a service but it doesn't work if he installs > PostgreSQL as a program (can anybody think of why this would make > a difference?). I found it just about impossible

Re: [BUGS] BUG #1547: CREATE TYPE AS error

2005-04-11 Thread Michael Fuhr
On Mon, Apr 11, 2005 at 08:21:45AM +0200, Diego Cattelan wrote: > > > >Can anybody else with a Windows system reproduce the > >problem? The messages in the links above are said to contain enough > >information to do so. > > windows XP pro SP2 > PostgreSQL 8.0.1 > > this is working for me (but n