From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Postgres Hackers List <hackers(at)postgresql(dot)org> |
Subject: | INSERT/DEFAULT VALUES broken? |
Date: | 1999-09-19 15:24:22 |
Message-ID: | 37E50026.EE334BD7@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom, can you check to see if
insert into <tablename> default values;
works on an unmodified current tree? I've got things ripped apart, but
I would have expected this to work, and am suspecting that it is a
problem introduced in your rewrite of this area a month or two ago.
(On a table without explicit default values, it should fill with
NULLs, but on my system I get an Assert failure because the target
list is never filled in.)
As usual, there is no coverage of this in the regression tests, so
there is no reason we should have caught this earlier... :(
- Thomas
--
Thomas Lockhart lockhart(at)alumni(dot)caltech(dot)edu
South Pasadena, California
From | Date | Subject | |
---|---|---|---|
Next Message | InfraRED | 1999-09-19 15:29:57 | when are indexes used? |
Previous Message | Thomas Lockhart | 1999-09-19 15:07:42 | Re: [HACKERS] All things equal, we are still alot slower then MySQL? |