Is it a bad idea to maintain a separate login sessions in MySQL and Code Behind?

Question

I have an application with C# code behind, which maintains a session state and has a value set for timeout and some redirect on session timeout logic in place.

Additionally, I have a MySQL requirement in which I am going to write triggers to store information about which logged in users last modified each table.

So, it seems that the easiest way to provide the triggers with a value for who is logged into the application, would be to copy the C# session to a MySQL session variable. This variable might not expire at the same time as the C# session does, but it will be reset each time a new person logs in.

Do you think there is another/better solution?

Answer 1

当任何用户登录后，然后在您的sql表中添加该用户的信息。