Magnus Hagander

Remove dependency on a specific Postgres user name in the results
 (Check result against CURRENT_USER with a boolean instead).

Change DEFAULT NULL to send back a NULL pointer
 rather than a string "NULL". This seems to work, where sending
 the string led to type conversion problems (and probably the wrong
 thing anyway).

Check for a constraint if is_sequence is set and omit making
 a UNIQUE index if so, since the primary key will cover that for us.

 rather than func_select_candidate().
Fix oper_select_candidate() to work with a single operator argument.
Repair left operator checking for null return from candidate list.

Forgot to remove README-1ST from the repository ...

tabularized a little bit...

A sort of 'log' of what operating systems are supported, and the date
last tested...

Change order of install...installing interfaces is the last to be done,
as, if not installing as root (which nobody *should* be doing, of course),
the perl install fails, which means that both bin and man directories
are not installed :(

This way, only thing that doesn't get installed is perl interface...

pg_operator problems.

Adds a few new keywords, but all are allowed as column names etc.

compiler to
attempt to compile libpq++.  The patches address the following problems:

1.  In my first pass at changing the libpq++ makefile, I forgot to
include the
    PORTNAME in the Makefile.in file.

2.  The UnixWare 7 C++ compiler did not like the '-K alloca' option in
CXXFLAGS.

Billy G. Allie

implementations of strtol() treat empty strings ("") as invalid arguments
while others convert this (erroneously, IHMO) to zero (0).  Assuming that the
expected behaviour of pg_atoi() is to return 0 if it is passed an empty
string, I am supplying the following patch to explictly check for an empty
string in pg_atoi() and return 0 if the string is empty.  The patch will also
trap a NULL character pointer being passed to pg_atoi() and will use elog() to
print out an error message if the input char pointer is NULL.


Billy G. Allie

1.  The UnixWare tas macro was reformatted (by indent or it like?) which caused
    it to break.  The asm macro construct is very particular about the %mem
    construct -- it has to start in column 1.

2.  When compiling libpq++, g++ was used even if configure found the C++ com-
    piler to be CC.

3.  When compiling libpq++, '-Wno-error' was added to CXXFLAGS, even if the
    compiler wasn't g++.

Billy G. Allie