This sounds like a good time to quote from someone much smarter than me.
If you're using eval, you're doing something wrong
You could store php code in a mysql column (and it doesn't have to be BLOB, it could be varchar or LONGTEXT). Then when you retrieve the said column, you could do something like this:
eval($row['phpcode']);
The problem here is security. What if inside that phpcode someone puts this:
highlight_file(__FILE__);exit;
Now guess what? They've got your database info & password out in the open. So now they can log in to your database, and wreak havoc. Not something you want to have happen.
The alternative is to keep php out of the mysql table, and use the table for what it was designed for: data. Keep data in the tables, let PHP handle the grunt of the logic (i.e. what's displayed where, etc.).
Now, if you wanted to get sums and totals and some basic conditional logic, you can do that in SQL with things like SUM() and COUNT() and CASE WHEN ... THEN ... ELSE ... END.
On another note...
In looking through you code, I see a giant security risk. Using user-inputted values directly into the SQL code is very dangerous. Currently if I went to your site and did sent the following in the query string:
?order=User&table=mysql.user
I could get a listing of all users in your mysql table. And with that a hash of their password, and what host they can connect from. So if you have a user which can connect from any host (i.e. their "Host" value is "%") and a simple password, I can figure out what their password is by looking in a hash table or just brute-forcing it in my own time. Then come back and modify the database outside the site. And if you follow the same mantra as most control panels and name the database similar to that of the ftp user, they might have access to the filesystem itself.
Just some things to think about.