Hi,
I think this is most surprising behavior -- shouldn't the UPDATE raise
an error?
alvherre=# create table foo (a int[]);
CREATE TABLE
alvherre=# insert into foo values (null);
INSERT 33649 1
alvherre=# update foo set a[3] = '42';
UPDATE 1
alvherre=# select a, a is null from foo;
a | ?column?
Alvaro Herrera wrote:
I think this is most surprising behavior -- shouldn't the UPDATE raise
an error?
Surprising, but not new (probably has been there back to the Berkley
code), and has come up before on one of the lists (I think it might even
have been pgsql-bugs).
regression=# select
On Wed, Feb 04, 2004 at 11:06:29AM -0800, Joe Conway wrote:
Alvaro Herrera wrote:
I think this is most surprising behavior -- shouldn't the UPDATE raise
an error?
Surprising, but not new (probably has been there back to the Berkley
code), and has come up before on one of the lists (I think
Alvaro Herrera [EMAIL PROTECTED] writes:
When is beta freeze supposed to happen?
AFAIK, no date has been set at all. I doubt we'll even think about it
until we see how the Windows port effort goes.
regards, tom lane
---(end of
