On Thu, May 18, 2006 at 10:35:48AM -0700, Joshua D. Drake wrote: > I understand the idea but I personally don't like it. I am not > really interested in cross-database compatible code. 9 times out of > 10 it is hacky, slow and lacks a solid supportable model because you > are always taking into account *the other* databases the application > supports. > > And to be frank, I don't think we should waste our time on MySQL. It > isn't a competitor, it just thinks it is. We should focus on our > real competition which is DB2, MSSQL, and Oracle. > > If we want to create contrib modules that have types etc... that > help port from Oracle to PostgreSQL or DB2 to PostgreSQL I am all > for it. > > The first thing that comes to mind is a set of domains that > implement Oracle types (names) as PostgreSQL types. > > Here's a start ;) > > postgres=# create domain varchar2 AS text; > CREATE DOMAIN > postgres=# create domain clob as text; > CREATE DOMAIN > postgres=# create domain blob as bytea; > CREATE DOMAIN > postgres=# create domain number as integer; > CREATE DOMAIN > postgres=#
postgres=# CREATE TABLE dual(); CREATE TABLE Cheers, D -- David Fetter <[EMAIL PROTECTED]> http://fetter.org/ phone: +1 415 235 3778 AIM: dfetter666 Skype: davidfetter Remember to vote! ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
