Intercepting User Actions at DB level before DB action, possible ?
Here's how i think things work :
On the back-end:
- when we set up the initial connection to the database, we specify a "privileged" user with certain DB privileges, usually all of them
- this "privileged" user is the one that is allowed to carry out DB insertions, deletions, i.e., actions which modify the DB
- there's also a DB "connection pool" which is composed of a group of these "privileged" users
On the front-end / gui:
- when a "normal" user performs an action that is going to require a DB action
- the request is sent to the DB
- the DB establishes a connection to the DB using one from the pool and performs the action
On the back-end:
- when we set up the initial connection to the database, we specify a "privileged" user with certain DB privileges, usually all of them
- this "privileged" user is the one that is allowed to carry out DB insertions, deletions, i.e., actions which modify the DB
- there's also a DB "connection pool" which is composed of a group of these "privileged" users
On the front-end / gui:
- when a "normal" user performs an action that is going to require a DB action
- the request is sent to the DB
- the DB establishes a connection to the DB using one from the pool and performs the action
0