MySQLi

[Karl DeSaulniers]

Hello All,
Hope this message finds you well. Quick question about MySQLi and PHP.
I have a website that was built back in 2012 that is still on PHP 5.2 and MySQL
and I am wanting to update it to PHP 5.7 with MySQLi without headaches.
I am dreading this like a spoonful of molasses. Is there any sugar remedy for this medicine
or do I just grow a pair and take it?

Any MySQL => MySQLi converters out there?
Any PHP5.2 => PHP 5.7 cheat sheets?

If I update my server to PHP 5.7 is everything going to break? Or stupid question of course it is?
lol

TIA,
Best,

Karl DeSaulniers
Design Drumm
http://designdrumm.com

[Lester Caine]

Post by Karl DeSaulniers
Hope this message finds you well. Quick question about MySQLi and PHP.
I have a website that was built back in 2012 that is still on PHP 5.2 and MySQL
and I am wanting to update it to PHP 5.7 with MySQLi without headaches.
I am dreading this like a spoonful of molasses. Is there any sugar remedy for this medicine
or do I just grow a pair and take it?

Well a few problems 5ere ...
PHP5.2 had already been shelved at end of 2010, but I know why it was
probably used 2 years later. I'm STILL running 5.2 on servers as the
time needed to convert those sites is just not available and can't be
justified cost wise :(

Post by Karl DeSaulniers
Any MySQL => MySQLi converters out there?
Any PHP5.2 => PHP 5.7 cheat sheets?
If I update my server to PHP 5.7 is everything going to break? Or stupid question of course it is?

PHP5.7 will not be around any time soon, PHP5.6 has just been released.
But converting from 5.2 all the way to 5.6 is not something that is easy
to do. I'm still only moving 5.2 to 5.4 at presnt.

http://php.net/manual/en/migration53.php and
http://php.net/manual/en/migration54.php is the starting point, but
things depricated in 5.3 were removed in 5.4 so if you are using any of
those methods then they need removing. You can switch the later PHP
servers to ignore e_strict warning/errors, but this is the major problem
area. and really the only way to move forward is clear all of those
problems before moving forward. Unless you caa ensure your server will
always be switched bak to a compatible mode of working.

And all that before even looking at MySQL ... I've never used it, so
hopefully someone else will cover that side.
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

[Karl DeSaulniers]

Post by Lester Caine

Post by Karl DeSaulniers
Hope this message finds you well. Quick question about MySQLi and PHP.
I have a website that was built back in 2012 that is still on PHP 5.2 and MySQL
and I am wanting to update it to PHP 5.7 with MySQLi without headaches.
I am dreading this like a spoonful of molasses. Is there any sugar remedy for this medicine
or do I just grow a pair and take it?

Well a few problems 5ere ...
PHP5.2 had already been shelved at end of 2010, but I know why it was
probably used 2 years later. I'm STILL running 5.2 on servers as the
time needed to convert those sites is just not available and can't be
justified cost wise :(

Post by Karl DeSaulniers
Any MySQL => MySQLi converters out there?
Any PHP5.2 => PHP 5.7 cheat sheets?
If I update my server to PHP 5.7 is everything going to break? Or stupid question of course it is?

PHP5.7 will not be around any time soon, PHP5.6 has just been released.
But converting from 5.2 all the way to 5.6 is not something that is easy
to do. I'm still only moving 5.2 to 5.4 at presnt.
http://php.net/manual/en/migration53.php and
http://php.net/manual/en/migration54.php is the starting point, but
things depricated in 5.3 were removed in 5.4 so if you are using any of
those methods then they need removing. You can switch the later PHP
servers to ignore e_strict warning/errors, but this is the major problem
area. and really the only way to move forward is clear all of those
problems before moving forward. Unless you caa ensure your server will
always be switched bak to a compatible mode of working.
And all that before even looking at MySQL ... I've never used it, so
hopefully someone else will cover that side.
--
Lester Caine - G8HFL

Ah, I see. Now Glob Design's comment makes sense.
Thanks Lester.

Best,

Karl DeSaulniers
Design Drumm
http://designdrumm.com

[Aziz Saleh]

Post by Karl DeSaulniers

Post by Lester Caine

Post by Karl DeSaulniers
Hope this message finds you well. Quick question about MySQLi and PHP.
I have a website that was built back in 2012 that is still on PHP 5.2

and MySQL

Post by Lester Caine

Post by Karl DeSaulniers
and I am wanting to update it to PHP 5.7 with MySQLi without headaches.
I am dreading this like a spoonful of molasses. Is there any sugar

remedy for this medicine

Post by Lester Caine

Post by Karl DeSaulniers
or do I just grow a pair and take it?

Well a few problems 5ere ...
PHP5.2 had already been shelved at end of 2010, but I know why it was
probably used 2 years later. I'm STILL running 5.2 on servers as the
time needed to convert those sites is just not available and can't be
justified cost wise :(

Post by Karl DeSaulniers
Any MySQL => MySQLi converters out there?
Any PHP5.2 => PHP 5.7 cheat sheets?
If I update my server to PHP 5.7 is everything going to break? Or

stupid question of course it is?

Post by Lester Caine
PHP5.7 will not be around any time soon, PHP5.6 has just been released.
But converting from 5.2 all the way to 5.6 is not something that is easy
to do. I'm still only moving 5.2 to 5.4 at presnt.
http://php.net/manual/en/migration53.php and
http://php.net/manual/en/migration54.php is the starting point, but
things depricated in 5.3 were removed in 5.4 so if you are using any of
those methods then they need removing. You can switch the later PHP
servers to ignore e_strict warning/errors, but this is the major problem
area. and really the only way to move forward is clear all of those
problems before moving forward. Unless you caa ensure your server will
always be switched bak to a compatible mode of working.
And all that before even looking at MySQL ... I've never used it, so
hopefully someone else will cover that side.
--
Lester Caine - G8HFL

Ah, I see. Now Glob Design's comment makes sense.
Thanks Lester.
Best,
Karl DeSaulniers
Design Drumm
http://designdrumm.com
--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

I am not sure about any MySQL -> MySQLI wrappers, but I did built a MySQL
-> PDO Wrapper a while back that you can use if you have PDO_MySQL enabled:

https://github.com/azizsaleh/mysql

[Karl DeSaulniers]

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.

Best,

Karl DeSaulniers
Design Drumm
http://designdrumm.com

Post by Aziz Saleh
https://github.com/azizsaleh/mysql

[Lester Caine]

Post by Karl DeSaulniers
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
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

[Karl DeSaulniers]

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

Post by Lester Caine

Post by Karl DeSaulniers
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

[Jasper Kips]

Post by Karl DeSaulniers
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

Post by Lester Caine

Post by Karl DeSaulniers
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

--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Problem with easy fixes is that they lead to tremendous problems. Best is to take the more difficult road, it'll be way quicker.
Yup off topic I know

Jasper

[Karl DeSaulniers]

Post by Jasper Kips

Post by Karl DeSaulniers
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

Post by Lester Caine

Post by Karl DeSaulniers
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

--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Problem with easy fixes is that they lead to tremendous problems. Best is to take the more difficult road, it'll be way quicker.
Yup off topic I know
Jasper
--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Truth. Thanks.

Best,

Karl DeSaulniers
Design Drumm
http://designdrumm.com