Re: INSERT/DEFAULT VALUES broken?

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: Re: INSERT/DEFAULT VALUES broken?
Date: 1999-09-19 16:26:18
Message-ID: 37E50EAA.29169BED@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.
> 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(at)alumni(dot)caltech(dot)edu
South Pasadena, California

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ryan Kirkpatrick 1999-09-19 16:29:14 Re: [PATCHES] Patches for alpha w. cc
Previous Message Tom Lane 1999-09-19 16:03:00 Re: [HACKERS] All things equal, we are still alot slower then MySQL?