It is a night mare
My MySQL 2 Tier database application written in vb.net connects to my database
the user privileges & security is handled by mysql it self with appropriate rights ( SELECT , UPDATE , INSERT & DELETE )
all are fine
THE NIGHT MARE IS
one of the client user has installed the MySQL client on his terminal and connected to MySQL server over the network with his UserId and Password and does all nonsense.
the tonnes of business logic gone into vein.
How do i tackle such situation please , do I need to alias the user details ? Or else ??? :confused:
My MySQL 2 Tier database application written in vb.net connects to my database
the user privileges & security is handled by mysql it self with appropriate rights ( SELECT , UPDATE , INSERT & DELETE )
all are fine
THE NIGHT MARE IS
one of the client user has installed the MySQL client on his terminal and connected to MySQL server over the network with his UserId and Password and does all nonsense.
the tonnes of business logic gone into vein.
How do i tackle such situation please , do I need to alias the user details ? Or else ??? :confused: