conflicting with the tutorial.sgml container document.

Instead of directly showing the random results, test the results
 for the expected behavior (range and randomness).

 in constraint clauses.
 IN and NOT IN only allow constaints, not subselects.
Jose' Soares' new reference docs pointed out the discrepency.
 Updating the docs too...

 in type checking for DEFAULT contraint clauses.
Could do more type coersion later...

From: Tom Lane <tgl@sss.pgh.pa.us>To: pgsql-patches@postgreSQL.org

Sigh.  That tweak needs a tweak --- I didn't realize that ".DEFAULT"
processing ignores dependencies, at least in the version of gmake I
have here (not sure if it's a bug or not).  Apply this patch aftermy previous one...

Just a couple of "after-commit" cleanups...

Date: Sun, 16 Aug 1998 14:56:48 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
Attached is a patch for this weekend's work on libpq.  I've dealt
with several issues:

        <for details: see message, in pgsql-patches archive for above data>

From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>

Here is some more contrib-fodder, based on TIH's IP address type,
for ISBN and ISSN identifiers (which I just happened to need to keep
track of the things in my library).

Previously, had thrown an error, but looking for alternate strategies
 for table indices utilization would prefer to continue.

Don't bother checking for alternate strategies if so
 since it was more likely a function or some other non-operator anyway.

Bracket things with #ifdef ENABLE_LINE_TYPE.
The line data type has always been used internally to support other types,
 but I/O routines have never been defined for it.

 removed from the man pages and put into the new sgml docs.

pgbuiltin.3 is obsolete for sure, and libpq.3 can become so since the
 size and scope of this man page is not appropriate in a man page format.

The "Oracle compatibility" page should have always been in with functions
 anyway. The BKI information is not really appropriate for a man page.

Make sure all files end with a newline.

Now back in sync with libpq.3 man page, which should be obsolete soon.

 and plans for some of them.

 on the mailing lists a while ago. Maybe slightly changed to fit docs.
Will go into the User's Guide.

 anyway, so this will replace them as of now.

Never seen because the parser frontend converts all trim() calls to
 btrim(), ltrim(), and rtime() calls before execution.

 indices for restriction clauses containing a constant.
Note that if an index does not match directly (usually because the types
 on both side of the clause don't match), and if a binary-compatible index
 is identified, then the operator function will be replaced by a new
 one. Should not be a problem, but be sure that if types are listed as
 being binary compatible (in parse_coerce.h) then the comparison functions
 are also binary-compatible, giving equivalent results.

 trouble, and the name of the shared library has been changed recently.
 Had to rerun ldconfig on my machine to get it working again.
Give an error message with a helpful hint if so...

    functions btrim() ltrim() and rtrim().

    The error was that the character after the set  was  included
    in the tests (ptr2 pointed to the character after the vardata
    part of set if no match found,  so  comparing  *ptr  or  *end
    against *ptr2 MAY match -> strip).


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being
right. # # Let's break this rule - forgive me.
# #======================================== jwieck@debis.com (Jan
Wieck) #

to understand cursors with variables.

Michael