Re: [pgsql-advocacy] Oracle buys Innobase - Mailing list pgsql-general

From Richard_D_Levine@raytheon.com
Subject Re: [pgsql-advocacy] Oracle buys Innobase
Date
Msg-id OFD2FCB0E2.76776F7E-ON0525709F.00526298-0525709F.00530C07@ftw.us.ray.com
Whole thread Raw
In response to Re: [pgsql-advocacy] Oracle buys Innobase  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [pgsql-advocacy] Oracle buys Innobase
Re: [pgsql-advocacy] Oracle buys Innobase
List pgsql-general

pgsql-general-owner@postgresql.org wrote on 10/19/2005 12:35:25 AM:

> Christopher Kings-Lynne <chriskl@familyhealth.com.au> writes:
> > Strangely a pgsql to oracle exporter is a good thing.  It'd be a great
> > feature of PostgreSQL.  Imagine how many people would start on
> > PostgreSQL if they KNEW that one day they could easily move to Oracle
if
> > they needed to.  Risk management.
>
> Problem is: to offer such a thing with a straight face, we'd have to
> confine ourselves to an Oracle-subset version of SQL.  For instance,
> lose the ability to distinguish empty-string from NULL.

Yep.  It is not just limited to empty strings; An all blank string, no
matter the number of characters, is stored as NULL.  And a corollary to
that idiocy is that a string with two blank characters is not equal to a
string with a single blank character in Oracle.  'a  ' is not equal to 'a
'.  'a ' is not equal to 'a'.  Port that to another database.  Seen the
JOIN syntax? *sigh*

Rick

>
>          regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings


pgsql-general by date:

Previous
From: "codeWarrior"
Date:
Subject: Re: Reverse engineering SW
Next
From: Tom Lane
Date:
Subject: Re: log_min_duration_statement oddity