"Uncommited transactions" appears when opening a view
Posted: Thu 26 Jul 2018 18:18
Hi everyone,
I have a view which produces an "Uncommited transactions" error message whenever I open it from within dbForgeStudio for MySQL on a remote machine. The message also has "Document: dorisdb_vwsearchresultsbasb.sql" ("dorisdb" being the database and "vwsearchresultsbasb" the view name )and "Transaction count: 1". The structure of the view appears to be fine, but when I did a backup and attempted to restore to another database on the same MySQL Server it complained about an unknown field. The unknown field is the field in the view as it was before I made a change to the view.
If I stop the MySQL Server and then restart it, I get the same error message when I open the view in dbForgeStudio. Note that if I run Workbench on the machine hosting the MySQL Server and open the view I get no error message.
I need to make some important further changes to the database and really, really do need to ensure I can back it up and restore it if anything goes wrong. How do I find out what is causing the problem and how do I stop it happening, please?
Please note that I only an occasional user of MySQL and am generally using this for data accessed by Microsoft Access.
I have a view which produces an "Uncommited transactions" error message whenever I open it from within dbForgeStudio for MySQL on a remote machine. The message also has "Document: dorisdb_vwsearchresultsbasb.sql" ("dorisdb" being the database and "vwsearchresultsbasb" the view name )and "Transaction count: 1". The structure of the view appears to be fine, but when I did a backup and attempted to restore to another database on the same MySQL Server it complained about an unknown field. The unknown field is the field in the view as it was before I made a change to the view.
If I stop the MySQL Server and then restart it, I get the same error message when I open the view in dbForgeStudio. Note that if I run Workbench on the machine hosting the MySQL Server and open the view I get no error message.
I need to make some important further changes to the database and really, really do need to ensure I can back it up and restore it if anything goes wrong. How do I find out what is causing the problem and how do I stop it happening, please?
Please note that I only an occasional user of MySQL and am generally using this for data accessed by Microsoft Access.