Re: INSERT/DEFAULT VALUES broken? - Mailing list pgsql-hackers

From Thomas Lockhart
Subject Re: INSERT/DEFAULT VALUES broken?
Date
Msg-id 37E50EAA.29169BED@alumni.caltech.edu
Whole thread Raw
In response to Re: INSERT/DEFAULT VALUES broken?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: INSERT/DEFAULT VALUES broken?  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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.
> It bombs for me too, so I suspect you are right that I broke it when
> I rearranged the analysis of INSERT.  It's probably a minor oversight
> someplace in there.
> Do you want me to fix it in current tree, or would it be wasted work
> considering that you are busy doing major parser rearrangements
> yourself?

If it isn't too much trouble, it would be great if you could look at
it. I'd like to stay focused on the join syntax (for inner joins at
the moment), but need to regression test things like this to make sure
new stuff hasn't introduced breakage...
                    - Thomas

-- 
Thomas Lockhart                lockhart@alumni.caltech.edu
South Pasadena, California


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] All things equal, we are still alot slower then MySQL?
Next
From: Ryan Kirkpatrick
Date:
Subject: Re: [PATCHES] Patches for alpha w. cc