Re: Problem with recent PostgreSQL relatedpressrelease

From: "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>
To: "Peter Eisentraut" <peter_e(at)gmx(dot)net>
Cc: pgsql-advocacy(at)postgresql(dot)org, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "Simon Riggs" <simon(at)2ndquadrant(dot)com>
Subject: Re: Problem with recent PostgreSQL relatedpressrelease
Date: 2007-07-16 12:22:43
Message-ID: 36e682920707160522w58338203nf9eebf60ac07b40@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

On 7/16/07, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> How are necessarily incompatible features such as the empty string vs. null
> handled?

In some of the Oracle-specific compatibility functions, we work around
stuff like NULL-concatenation. But PostgreSQL's method is maintained
and the default.

--
Jonah H. Harris, Software Architect | phone: 732.331.1324
EnterpriseDB Corporation | fax: 732.331.1301
33 Wood Ave S, 3rd Floor | jharris(at)enterprisedb(dot)com
Iselin, New Jersey 08830 | http://www.enterprisedb.com/

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Federico 2007-07-16 13:56:52 Re: Thank you for PGDay
Previous Message Peter Eisentraut 2007-07-16 12:11:22 Re: Problem with recent PostgreSQL relatedpressrelease