On 1-May-04, at 2:04 AM, Hans-Jürgen Schönig wrote:
Doesn't your patch cause problems with the PostgreSQL ODBC driver
which adds [...]
I don't think this will cause an error (I tried it locally, and pg_proc
rows for the new functions are installed, but power() and ceiling()
continue to work).
I've written a small patch that could be useful for people with old
applications, since it restores the original behaviour of silently treating
empty strings as 0 (at least for integers). It introduces a new bool GUC
variable empty_equals_0 with default off. With a simple SET
empty_equals_0 to
Dear patchers,
please find attached a small patch for adding new aggregate functions:
(1) boolean-and and boolean-or aggregates named bool_and and bool_or.
they correspond to standard sql every and some/any aggregates.
they do not have the right name as there is a problem with
the
On Sat, May 01, 2004 at 04:21:21PM +0200, Fabien COELHO wrote:
(2) bitwise integer aggregates named bit_and and bit_or for
int2, int4, int8 and bit types. They are not standard,
however they exist in other db (eg mysql), and I needed them
for some other stuff.
I'm sure people
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
Right at the moment I am thinking we may end up keeping only about one
file out of the existing src/timezone import, so maybe it doesn't need
a whole subdirectory anyway?
We will still need the timezone database files.
Good point, I
Bruce Momjian [EMAIL PROTECTED] writes:
Digging into getting this working on unix, it seems the configure tests
that look at /usr/include are then setting values related to timezone
that don't apply to src/timezone code. Not sure how I am going to fix
that.
You rip 'em all out is how. If we
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Tom Lane wrote:
Right at the moment I am thinking we may end up keeping only about one
file out of the existing src/timezone import, so maybe it doesn't need
a whole subdirectory anyway?
We will still need the timezone database
