I can't speak for the MySQL people, but in my view your "workaround" is the
correct way of implementing this. It is not the database's job to keep track
of which user wants to keep what session open, and HTTP is stateless by
design. Keeping transactions open for relatively long periods of time woul
CR: add support of interactive transactions for webclients
Hello,
I dont know how to place an idea (CR) for mySQL.
I try it that way.
At the moment I am implementing an "easy-to-use" multiuser webclient for
database usage.
(phpMyAdmin in contrast is a very powerful tool for p
