Re: [phpesp-dev] Port to ODBC

[Stefan C. <sch...@ea...>]

> Because of the way you've rewritten the logic processing in some of the
> code (for ex. mysql_num_rows), we'll need to take a good look at the time
> it would take to rewrite phpesp to use that logic vs time to use the
> structures, triggers, and sequencers that I've developed.

heeemmm her.. Yes maybe whyn not ? :)

I'm done now, just expecting the move to Oracle to happen soon. Overall, 
moving to PostgreSQL wasn't that hard. Just very time consuming. It took me 
roughly 10 days, using triggers to emulate auto_increment and a bit of glue 
to avoid "last_insert_id". PostgreSQL also let me use foreign keys like hell, 
although it costs some performance, I think that data integrity is nice to 
have (mySQL documentation about foreing keys is kind of scary).

On the PEAR side, since I saw that it doesn't help me a lot in the porting 
area, I think that using ODBC was a good idea : the parts explained above had 
to be done anyway, PEAR or not.

>  These structures
> that I've incorporated into the ORACLE schema would probably be more easily
> used to rewrite the phpESP mysql function calls.  I say this only because
> I'm more familiar with triggers, sequencers and things needed in Oracle.  

Those where helpful, this is the one I've used :

CREATE SEQUENCE global_id;

CREATE OR REPLACE FUNCTION get_unique_id() RETURNS TRIGGER AS '
   BEGIN
      IF NEW.id IS NULL THEN
          NEW.id = nextval(''global_id'');
      END IF;
      RETURN NEW;
   END;
   ' LANGUAGE 'plpgsql';


stF



> We'll need to compare notes on this as you've now more expertise in
> PostgreSQL.  BTW: is PostgreSQL formally supported with the PEAR DB stuff?
>
> I've only got a couple responses to "call for developers" on the PORT to
> PEAR DB.    Isn't there anyone else that would be interested?
>
> >>> "Stefan Champailler" <sch...@ea...> 11/06/03 03:57AM >>>
>
> Continuing port to PostgreSQL on IIS. I think that the ODBC layer has
> troubles if one doesn't call "odbc_free_result" properly. Be aware of that
> because not doing so (if that is the problme, I can hardly prove that)
> tends to lead to very strange behaviour.
>
> I'm also almost done with rewriting the DB tables. I'll send them here when
> they'll be up and running on Oracle.
>
> stF
>
> > Continuing my work to port phpESP to ODBC/Oracle, I stumbled against a
> > few problem because phpESP was primarily developped for mySQL. When
> > moving to Oracle beware that there's no auto_increment and thus we must
> > use sequence. To be able to predevelop outside the heavily controlled
> > Oracle environment, I figured out that it'd be better if I used
> > PostGreSQL, because it provides sequences and, more importantly, good
> > support for subqueries (an area where MySQL traps you way too much in its
> > own DB paradigm (IMHO)). Therefore, I'mprobably going to try to port
> > everything to PostgreSQL and when I'm done, I'll move everything to
> > Oracle. Again, it may sound a little overkill, but the DBA are so
> > reluctant/busy to leave me alone in a ORA sand-box that I have to go my
> > own way.
> >
> > stF
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: SF.net Giveback Program.
> > Does SourceForge.net help you be more productive?  Does it
> > help you create better code?   SHARE THE LOVE, and help us help
> > YOU!  Click Here: http://sourceforge.net/donate/
> > _______________________________________________
> > phpESP-devel mailing list
> > php...@li...
> > https://lists.sourceforge.net/lists/listinfo/phpesp-devel
>
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?   SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> phpESP-devel mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpesp-devel
>
>
>
> ---------------------------------------------------------------------------
>--- This message may contain confidential information, and is intended only
> for the use of the individual(s) to whom it is addressed.
>
>
> ===========================================================================
>===