> >>>> insert into <tablename> default values;
> Nope, not a parser problem at all; rewriter brain damage. It's been
> broken at least since 6.4, but only if you do INSERT ... DEFAULT VALUES
> into a table that has no columns with default values, and only if you
> have Asserts turned on (so the average user wouldn't see it anyway).
> Fix is to dike out incorrect Assert...
Sorry about that; I usually don't run with Assert enabled, so wouldn't
have caught it earlier. Thanks for looking into it.
- Thomas
--
Thomas Lockhart lockhart@alumni.caltech.edu
South Pasadena, California
