This will almost definitely be a breaking change, and large parts of gazelle will need to be modified to use the new class.
Current plan is to write a new class completely while leaving the old class in tact for legacy purposes, and steadily migrating all uses of the old class to the new one. This way we don’t have to deal with writing a class backwards compatible with the old class.
This will almost definitely be a breaking change, and large parts of gazelle will need to be modified to use the new class.
Current plan is to write a new class completely while leaving the old class in tact for legacy purposes, and steadily migrating all uses of the old class to the new one. This way we don't have to deal with writing a class backwards compatible with the old class.
Using some nice syntactical features of PHP7, we’ve added prepared statement support to the current database class in a backwards compatible way, and are now slowly migrating existing queries.
Using some nice syntactical features of PHP7, we've added prepared statement support to the current database class in a backwards compatible way, and are now slowly migrating existing queries.
Should probably just extend mysqli instead of being a wrapper
Definitely needs to start exposing methods for prepared statements
This will almost definitely be a breaking change, and large parts of gazelle will need to be modified to use the new class.
Current plan is to write a new class completely while leaving the old class in tact for legacy purposes, and steadily migrating all uses of the old class to the new one. This way we don’t have to deal with writing a class backwards compatible with the old class.
Using some nice syntactical features of PHP7, we’ve added prepared statement support to the current database class in a backwards compatible way, and are now slowly migrating existing queries.