Re: MySQLi
| From: | Karl DeSaulniers | Date: | Sun, 14 Sep 2014 23:08:50 +0000 |
| Subject: | Re: MySQLi | ||
| References: | 1 2 3 4 5 6 | Groups: | php.db |
| Request: | Send a blank email to php-db+get-48927@lists.php.net to get a copy of this message | ||
Procedural php. Haven't had a chance to learn OOP. Would love to though. : /
I think I may be moling it a bit too. Guess I was hoping for an easy fix, don't judge me.. :P
Thanks for all your responses everyone.
Best,
Karl DeSaulniers
Design Drumm
http://designdrumm.com
On Sep 14, 2014, at 2:48 AM, Lester Caine <lester@lsces.co.uk> wrote:
> On 14/09/14 04:57, Karl DeSaulniers wrote:
>> Awesome, thanks for the link. I know even less about PDO then I do regular MySQL however.
>> I am hoping MySQLi isn't too far off a shoot. Just need to sit down with it all and
>> figure out a path.
>
> PDO is still a bit of a grey area. It was intended to make changes
> between database engines more transparent, and MySQL to MySQLi is
> essentially just a different front end both targeting MySQL. The problem
> is that it only ever did half the job, trying to make the data returned
> 'transparent' while ignoring the SQL. Aziz's approach is one way of
> going, but just like the e_strict problems with PHP itself, it's the
> subtle changes to the language used which cause problems when
> 'translating' from one to the other. It will depend on the style of
> MySQL you are using currently as to how easy it is to 'translate'. My
> own database is Firebird which has SQL functions that have yet to appear
> in MySQL, some of those are exposed in MySQLi so you can ignore them
> when upgrading but it is always those fringe cases that take the most
> time to resolve? :(
>
> --
> Lester Caine - G8HFL