ezRPG Community Development

[JakeB]

ezRPG is now allowing it's members to take part in development of the engine.

 

To contribute to the ezRPG project just follow these simple steps:

 

1. Fork the project (http://github.com/ezrpg/ezrpg)

2. Make your changes, and push them to your forked repository

3. Send a pull request with your changes

4. We will review your changes, and accept them if they fix the problem without causing any problems

[Guest]

Any reason for using mysql and not PDO or MySQL(i)? Also maybe fix the commenting? @return, @todo, @param ect

[JakeB]

I'm not sure why zeggy didn't use mysqli when he developed it originally, but in the next release i plan to have a MySQLi class for it.

[Guest]

Ah cool. keep the mysql one though incase some people for a strange reason don't have the improved one. On install decide which to use :)

[Aventro]

No, don't. If people still have a version NOT supporting MySQLi it's about time upgrading, it's shameful using anything less than 5.3!

[a_bertrand]

Well... Here I don't agree, not all run with "new" versions of PHP. Actually if you run on older Cent OS or old Redhat based distro you could still have PHP 5.1, so always running for the latest and greatest may cut you out of some. Yet I would say MySQLi is a must, and old MySQL is really to be avoided. But that's personal opinion.

[Guest]

True MySQLi should be used if not PDO, however as AB said not all places use > 5.3. MySQL is just a safe backup

[Aventro]

Well... Here I don't agree, not all run with "new" versions of PHP. Actually if you run on older Cent OS or old Redhat based distro you could still have PHP 5.1, so always running for the latest and greatest may cut you out of some. Yet I would say MySQLi is a must, and old MySQL is really to be avoided. But that's personal opinion.

Perhaps they do, but still I don't see a reason why to keep the development in the "back" when we can put it forward!

[JakeB]

We will be keeping mysql support, we will just add a mysqli driver to the current dbfactory.

[Spudinski]

Well... Here I don't agree, not all run with "new" versions of PHP. Actually if you run on older Cent OS or old Redhat based distro you could still have PHP 5.1, so always running for the latest and greatest may cut you out of some. Yet I would say MySQLi is a must, and old MySQL is really to be avoided. But that's personal opinion.

Even the last CentOs major shipped with PHP 5.3.2(/3?). The industry standard is PHP 5.3.3.

ext/mysql is the devils work. It's bad on so many levels, I'm not going to explain.

Furthermore, procedural ext/mysqli is going to be dropped from PHP in the near future.

PHP is aiming for Pdo, and rightfully so, it does have a better abstraction layer for using multiple adapters(DBMS').

[SC-Scripting]

Shared hostings can not update there PHP version ;)

Only with VPS/Dedicated servers.

So better to keep mysql in it.

[Spudinski]

Shared hostings can not update there PHP version ;)

Only with VPS/Dedicated servers.

So better to keep mysql in it.

-facepalm-

[Dave]

Shared hostings can not update there PHP version ;)

Only with VPS/Dedicated servers.

So better to keep mysql in it.

That's not true at all, contact your host they can normally enable certain versions for your account.

[SC-Scripting]

Thats another thing ;)

But i was meaning by default...

[Spudinski]

-facepalm-

-facepalm- do-over.