Re: [BUGS] COPY fails on 8.1 with invalid byte sequences in text

2006-11-03 Thread Dennis Bjorklund
Tom Lane skrev: Is this not a bug? I don't actually see that it is. The documentation is perfectly clear on the point: (It is your responsibility that the byte sequences you create are valid characters in the server character set encoding.) (This is in 4.1.2.1. String Consta

[BUGS] LOAD broken?

2003-09-06 Thread Dennis Bjorklund
I've got a C function in a .so that I use in postgres. While developing it I want to reload the dynamic library. The docs says that LOAD should do the trick but nothing happens when I use it. Have LOAD stoped working and is it now a NOP? I've tried LOAD both when the function exists in pg, and

[BUGS] 7.5devel - duplicate error message

2003-11-16 Thread Dennis Bjorklund
In current cvs I get dennis=# CREATE FUNCTION foo () returns int AS 'select a;' language 'sql'; ERROR: column "a" does not exist ERROR: column "a" does not exist It should only be one error. -- /Dennis ---(end of broadcast)--- TIP 7: don't for

Re: [BUGS] 7.5devel - duplicate error message

2003-11-16 Thread Dennis Bjorklund
On Sun, 16 Nov 2003, Kris Jurka wrote: > > It should only be one error. > > Is there any chance you started the postmaster in the background and then > started psql on the same terminal so you get one error reported to the > server and one to the client? There is a very big chance that I did :-)

[BUGS] NULL in arrays

2004-01-15 Thread Dennis Bjorklund
A person (cross) in the irc channel have found a bug with the new arrays. Here is what I did to reproduce: dennis=# CREATE TABLE foo (a int[]); CREATE TABLE dennis=# INSERT INTO foo VALUES (ARRAY[2,NULL]); INSERT 25353 1 That last insert contains a NULL value which are not allowed in arrays and

Re: [BUGS] NULL in arrays

2004-01-15 Thread Dennis Bjorklund
On Thu, 15 Jan 2004, Dennis Bjorklund wrote: > A person (cross) in the irc channel Actually, he calls himself crass which is the only name I have :-) Not very important, but I like things to be correct (when I can). -- /Dennis Björklund ---(end of broadc

Re: [BUGS] NULL in arrays

2004-01-15 Thread Dennis Bjorklund
On Thu, 15 Jan 2004, Tom Lane wrote: > > dennis=# INSERT INTO foo VALUES (ARRAY[2,NULL]); > > INSERT 25353 1 > > > That last insert contains a NULL value which are not allowed in arrays and > > yet a insert is performed. The table contains a NULL value afterwards > > (and no array). > > As we u

Re: [BUGS] NULL in arrays

2004-01-15 Thread Dennis Bjorklund
On Thu, 15 Jan 2004, Joe Conway wrote: > Additionally, this behavior was discussed during the 7.4 development and > beta cycles on at least a couple occassions -- that would have been the > time to complain, not now. Well, I will complain whenever I see something I don't like :-) Just because

Re: [BUGS] NULL in arrays

2004-01-15 Thread Dennis Bjorklund
On Thu, 15 Jan 2004, Joe Conway wrote: > I agree, and see Tom does too in a nearby post. Do you want to propose > some wording, or just leave it up to me? You do it, and I'll just complain later if I don't like it :-) I still think it's a strange behaviour, but as long as it's documented it's

Re: [HACKERS] [BUGS] BUG #1290: Default value and ALTER...TYPE

2004-10-21 Thread Dennis Bjorklund
On Thu, 21 Oct 2004, Tom Lane wrote: > > Would it be possible to check the compatibility of a default value for > > the associated column? > > I think that would introduce as many problems as it would fix. AFAICS > the only way to make such a check is to evaluate the expression and see > what ha

Re: [HACKERS] [BUGS] BUG #1290: Default value and ALTER...TYPE

2004-10-24 Thread Dennis Bjorklund
On Sun, 24 Oct 2004, Neil Conway wrote: > (1) Accept the default's raw parsetree from the parser > (2) Convert it to a cooked parsetree via transformExpr() > (3) Add a coercion to the table's column type > > Can't we save the cooked parsetree that we produced in #2? One could even save the strin

Re: [HACKERS] [BUGS] BUG #1290: Default value and ALTER...TYPE

2004-10-24 Thread Dennis Bjorklund
On Sun, 24 Oct 2004, Tom Lane wrote: > > (1) Accept the default's raw parsetree from the parser > > (2) Convert it to a cooked parsetree via transformExpr() > > (3) Add a coercion to the table's column type > > > Can't we save the cooked parsetree that we produced in #2? > > Not without an initd

[BUGS] Table name used as aggregate argument

2005-02-07 Thread Dennis Bjorklund
How come this work in pg (8.0 and older): CREATE TABLE bug (x int); SELECT count(bug) FROM bug; Shouldn't it complain and say that "bug" is not a column? -- /Dennis Björklund ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ

[BUGS] set returning function

2005-05-09 Thread Dennis Bjorklund
An issue came up on irc. How come that this work: SELECT generate_series(0,1); but SELECT foo(0,1); does not, where foo is my own set returning function, like this example: CREATE FUNCTION foo(a int, b int) RETURNS setof int AS 'BEGIN RETURN NEXT a;

Re: [BUGS] set returning function

2005-05-09 Thread Dennis Bjorklund
On Mon, 9 May 2005, Tom Lane wrote: > > Bug? > > Unimplemented feature. Is SELECT 42, srf(); the same as SELECT 42, * FROM srf(); ? In my view the first version is an error. It's not like you can put a normal table in the select list, so why can we put a set returning function there?