MySQLi Extended Class

Currently building a MySQLi Extended Class in PHP.

GitHub
https://github.com/Clawed/MySQLiExtended

Features
- Prepared Statements
-- Insert - Complete
-- Select - Not started, trying to work how to do it.
-- Update - Complete
-- Delete - Complete

Feedback
- This would be appreciated.

Just a question, why aren't you putting the connect in __construct and the disconnect in __destruct? Makes more sense to have this handled automatically. I mean, the connection is closed regardless of calling mysql_close, just an observation.

Yea i know, it's only like that because when i was building query builder, i kept getting connection errors, when i wasn't even intending of a connection.

I will be changing it sometime later today.

It would only connect when the class was called, and there isn't a reason for the class to be called unless a database connection is intended.

Quote:

---

Originally Posted by Ron

It would only connect when the class was called, and there isn't a reason for the class to be called unless a database connection is intended.

---

Yep, It'll only be called upon request, so it will only connect upon query & stuff.

You should include anti sql injection. This would be the main reason to use a class instead of plain SQL.