"Thomas G. Lockhart" <lockhart(at)alumni(dot)caltech(dot)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
The thing that is "strange" is that you get nonunique values of i,
which is definitely a bit unexpected for "SELECT DISTINCT":
play=> SELECT * FROM dtest;
play=> SELECT DISTINCT i FROM dtest ORDER BY j;
The reason that this is happening is that the "distinct" filter is
actually being run on i,j not just i (see "distinct + order by" thread
in the hackers archives around 8-Nov-98).
I don't know whether the SQL standard defines how this combination of
features ought to work ... but our current behavior seems fairly
>> * 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...
regards, tom lane
pgsql-hackers by date
|Next:||From: Terry Mackintosh||Date: 1998-12-19 18:30:10|
|Subject: Is this a bug? or am I doing some thing wrong?|
|Previous:||From: Trever Adams||Date: 1998-12-19 11:51:12|
|Subject: BUGS list|