Re: [HACKERS] Upgrades for 6.4.1

> "Thomas G. Lockhart" <lockhart@alumni.caltech.edu> writes:
> >> * SELECT DISTINCT i FROM dtest ORDER BY j generates strange output
> 
> > In my simple test case, it orders by j, then only shows i. Is that
> > strange?
> 
> The thing that is "strange" is that you get nonunique values of i,
> which is definitely a bit unexpected for "SELECT DISTINCT":
> I don't know whether the SQL standard defines how this combination of
> features ought to work ... but our current behavior seems fairly
> surprising...

Re-added to TODO list.

> 
> 
> >> * Allow constraint NULL just as we honor NOT NULL
> 
> > Fundamental yacc problem with this as I recall. Gives rise to
> > shift/reduce problems since it is ambiguous with other uses of "NULL" in
> > the same area.
> 
> More to the point, what possible use would a column constrained to NULL
> be?  Might as well just not have it in the table...

It just says the column _may_ accept nulls.  It is the default anyway.

--  Bruce Momjian                        |  http://www.op.net/~candle maillist@candle.pha.pa.us            |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026