benanamen

Just to clarify, my response had nothing to do with MVC. It was with the Database Class itself.

Typically yes, that's what you see out on the net, but I would have to disagree with this method. IMO there is really only two common cases to use Try/Catch, that being the DB Connection and handling a duplicate constraint error. There is no need to litter the code base with Try/Catch blocks. (Yes, I was guilty of that until I got spanked by @Jacques1 and learned better) What "should" be done is set the PDO::ATTR_ERRMODE => PDO::ERRMODE_EXCEPTION and let the exceptions bubble up and let PHP handle it, which it does very well. set_exception_handler can also be used if you want a custom handler for exceptions.

Link please. Based on the DB class, the tutorial is less than optimal.

If you want a count, then SELECT a count.

In a single form? That sounds like quite a lot. What exactly do you have going on?

That particular tutorial has issues.

You need to implement PRG. (POST, REDIRECT, GET)

You may also want to look into Temporal Data Tables or Audit Logging depending on your specific needs.

The best way to do DB backups is not with PDO. What you want to do is write a shell script that acts directly on the DB and set up a CRON job to run it at whatever intervals.

The first thing you need to do is stop mixing obsolete mysql_* code with mysqli.

If you passed it in as a parameter you would never have to edit anything and could use the function for any currency

I have been using MVP (Model - View - Presenter) for some time. Works quite well.

By the way, your test_input function is a block of code from the 90's that needs to be taken behind the barn and shot and buried forever. Surprised to still see that floating around. Additionally, NEVER EVER put variables in your query. You need to use prepared statements

What is this "bridge" you created? What do you mean "doesn't allow direct access to mysql Server"? What does Mysql have to do with where you are putting your Php code?