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

[Charlie S. <Sm...@ld...>]

I would also think we'd separate DB schema/scripts/logs for each database =
type.
The use of the ENUM type in mysql vs a check constraint in Oracle vs ? in =
PostGreSQL.

I would also advocate tying down the schema before proceeding with a rewrite
of phpESP to accomodate PEAR DB.   After the schema is tied down, we could =
delve into=20
translating the mysql calls to the PEARDB calls, and proceed with unit =
testing, if that sounds ok to=20
you guys.

I've written a perl script that reads from a sqldump/export from phpMyAdmin
and creates an Oracle schema for all the tables, triggers, indexes, =
sequencers.
So making modifications to what we want to do with the Oracle schema should
be fairly easy to make for all the tables.

I've also written a perl script to translate mysql function calls to =
routines I've written, which in turn make calls to OCI8/Oracle.  This scrip=
t=
 can be modified to translate the mysql functions to the =
PEARDB/MDB::functions().   We'll need to identify a PEARDB function for eac=
h=
 of the mysql functions that we have in the code, and identify any =
additional fields that would be needed.


With that:  =20
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




>>> "Matthew Gregg" <gr...@mu...> 09/30/03 11:19AM >>>
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=20
> noticed right away was the database creation scripts.  Are we going to=20
> write one for each database we want to support, or is there some way to=20
> generically specify a database design?  One thing that caught my eye=20
> was the use of the ENUM type which is common in mySQL, but doesn't=20
> exist is PostgreSQL.  However, it looks like all the ENUMs just hold=20
> two values, Y and N, which would map to the boolean type (true,false)=20
> in PostgreSQL.  This will also affect the code, so I think it's=20
> something we should work out sooner rather than later.
>=20
>=20
> On Tuesday, September 30, 2003, at 07:27 AM, Charlie Smith wrote:
>=20
> >Looks like Jeremy Buchmann and I (Charlie Smith) could work on the=20
> >PEAR port right away.   Could we discuss this possibility?
> >
> >>>>"Matthew Gregg" <gr...@mu...> 09/29/03 09:02AM >>>
> >http://pear.php.net=20
> >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=20
> >>an effort to port to PEAR compliant DB?
> >>
> >>I've a question with regards to how the NOT NULL default '' fields=20
> >>would be defined in the PEAR description?
> >>I'd be inclined to define these types of fieds as NOT NULL in Oracle=20
> >>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=20
> >>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=20
> >>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=20
> >>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
> >>
>=20
>=20
>=20
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf=20
> _______________________________________________
> phpESP-devel mailing list
> php...@li...=20
> https://lists.sourceforge.net/lists/listinfo/phpesp-devel=20
>=20

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


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf=20
_______________________________________________
phpESP-devel mailing list
php...@li...=20
https://lists.sourceforge.net/lists/listinfo/phpesp-devel=20


---------------------------------------------------------------------------=
---
This message may contain confidential information, and is intended only for=
 =
the use of the individual(s) to whom it is addressed.


=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D