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

[Matthew G. <gr...@mu...>]

Probably going to have to create/maintain DB creation scripts for each
DB we plan on supporting.  Changes made to ESP also should be done in
a way that supports the all "supported" DB's.  With mySQL as a given, I
would target Postgres and Oracle as the supported databases.

On Tue, Sep 30, 2003 at 09:56:26AM -0700, Jeremy Buchmann wrote:
> I can start fairly soon, assuming we decide to use phpESP.  One thing I 
> noticed right away was the database creation scripts.  Are we going to 
> write one for each database we want to support, or is there some way to 
> generically specify a database design?  One thing that caught my eye 
> was the use of the ENUM type which is common in mySQL, but doesn't 
> exist is PostgreSQL.  However, it looks like all the ENUMs just hold 
> two values, Y and N, which would map to the boolean type (true,false) 
> in PostgreSQL.  This will also affect the code, so I think it's 
> something we should work out sooner rather than later.
> 
> 
> On Tuesday, September 30, 2003, at 07:27 AM, Charlie Smith wrote:
> 
> >Looks like Jeremy Buchmann and I (Charlie Smith) could work on the 
> >PEAR port right away.   Could we discuss this possibility?
> >
> >>>>"Matthew Gregg" <gr...@mu...> 09/29/03 09:02AM >>>
> >http://pear.php.net
> >On Mon, 2003-09-29 at 10:18, Charlie Smith wrote:
> >>Where is the API located for PEAR?
> >>
> >>Could the work I'm doing on an OCI8 (Oracle)  rewrite go to help in 
> >>an effort to port to PEAR compliant DB?
> >>
> >>I've a question with regards to how the NOT NULL default '' fields 
> >>would be defined in the PEAR description?
> >>I'd be inclined to define these types of fieds as NOT NULL in Oracle 
> >>and let the code or a trigger fill in the value
> >>with something if needed.   Any opinions?
> >>
> >>I'm sorry, I'm not familiar with the PEAR API.  Is this just a 
> >>supporting library of php code?
> >>
> >>
> >>
> >>>>>"Jeremy Buchmann" <je...@we...> 09/25/03 11:29AM >>>
> >>Hi all,
> >>
> >>I'm evaluating the use of phpESP for my company and have a few quick
> >>questions.
> >>
> >>First, we use PostgreSQL for all our database needs.  Since phpESP 
> >>uses
> >>mySQL, we would either have to port it to PostgreSQL or assist in the
> >>port to PEAR.  I'm experienced in PHP/PostgreSQL, and I think based on
> >>the number of lines in the code base that have 'mysql' in them, that I
> >>could do a port to PostgreSQL in 1-2 weeks.  I'd rather not fork from
> >>the main distribution, so ideally I'd like to help in the port to 
> >>PEAR,
> >>but I've never used PEAR.  With a quick glance at the API, it looks
> >>easy enough...fairly similar to Perl's DBI.  So my questions are, how
> >>is the PEAR port coming along?  Would my help be welcome and useful?
> >>Would phpESP only use the database parts of PEAR?
> >>
> >>Thanks,
> >>Jeremy
> >>
> 
> 
> 
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> phpESP-devel mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpesp-devel
> 

-- 
mcg
-------------------------------------
The IT Lab (http://www.itlab.musc.edu)