character in identifiers.  The first change eliminates the current need
to put spaces around parameter references, as in "x<=$2".  The second
change improves compatibility with Oracle and some other RDBMSes.  This
was discussed and agreed to back in January, but did not get done.

match the SQL standard.  Document FLOAT and FLOAT(p) notations in
datatype.sgml.  Per recent pghackers discussion.

siblings.

work at all, and neither case behaved sanely for negative intervals.

silently resolving them to type TEXT.  This is comparable to what we
do when faced with UNKNOWN in CASE, UNION, and other contexts.  It gets
rid of this and related annoyances:
	select distinct f1, '' from int4_tbl;
	ERROR:  Unable to identify an ordering operator '<' for type unknown
This was discussed many moons ago, but no one got round to fixing it.

some cases of redundant clauses that were formerly not caught.  We have
to special-case this because the clauses involved never get attached to
the same join restrictlist and so the existing logic does not notice
that they are redundant.

hopefully a little more useful.

both clauses specify the same targets, rather than always using the
default ordering operator.  This allows 'GROUP BY foo ORDER BY foo DESC'
to be done with only one sort step.

Lee Kindness

Lee Kindness

- Compatibility functions for INFORMIX handling of DECLARE statement.

not a SELECT.  We didn't use to allow that, but we do now.

on some platforms.

Compiles on BCC 5.5 and VC++ 6.0 (with warnings).

Karl Waclawek

Also quickly added mention that it may be a qualified schema name.

Rod Taylor