Re: [phpesp-dev] Porting to PEAR and/or PostgreSQL

[Jeremy B. <je...@we...>]

On Wednesday, October 1, 2003, at 02:13 PM, Stefan Champailler wrote:
>> With that:
>> Let's discuss how to handle the schemas
>> 1) ENUM type in PostGreSQL and Oracle.
>> 2) the empty string in default values
>> 3) default values vs NOT NULL
>
> My Oracle and PostgreSQL is limited, so I ask the question : are we 
> planning
> to make severeal schema with the hope to have minimum code rewrite on 
> the
> phpESP side ? (I guess it makes sense).
>

I think it's best to work out a schema that:

   1. Is as generic as possible so we can avoid or minimize code like 
this:

       if ($DB == "mysql") {
         do something...
       }
       elseif ($DB == "postgresql") {
         do something else...
       }
       elseif ($DB == "oracle") {
         etc, etc
       }

   2. Is still functionally the same as the current one (I don't think 
anyone wants to get into a database redesign).  Let me clarify 
that...it's not just functionally the same, it is the same except we 
may change some data types to something more generic and rename some 
fields to avoid keyword collisions.

So it would be the same generic schema for each database, but different 
creation scripts and things like that.  At least, that's how I envision 
it.

--Jeremy