Moviemanager itself seems to be unable to recognize missing tables + create them and consequently spews some errors + scary java backtraces of the kind
ERROR net.sf.xmm.moviemanager.database.Database.getActiveAdditionalInfoFields(Database.java:548)
Exception:
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'moviemanager_test.Settings' doesn't exist
at ...
on startup
You can try to create a new entry when running MovieManager with this new database, but saving will just delete all field data and not save any new entries.
Workaround:
Have some old Moviemanager-database sitting around or download some very old version of MovieManager and create one + fill it with at least one entry, then do a
You can now use the file moviemanager_database.template.sql file to create the necessary tables by sourcing it into any new database you create (yes, I'm using several ;-).
Anyhow, thanks alot for this great program :D
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just tested on Ubuntu with MySQL 5.1.41, and latest version of MeD's Movie Manager, and it worked.
It's really strange that it works for you on an older version and not the latest. Have you tried to create the database using the root user?
Could you post the content of the log file from where the database is created?
Bro
Bro
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Strange indeed. I'm running OpenSUSE 11.3 on both mysql-Server and MovieManager-clients (MySQL 5.1.46). I'm sorry, but there is no logfile, at least I can't find one ;-)
What I did serverside was the sequence:
su
mysql -p
mysql> CREATE USER 'moviemanager'@'%' IDENTIFIED BY 'secret';
mysql> CREATE DATABASE moviemanager_test;
mysql> GRANT ALL ON moviemanager_test.* TO 'moviemanager'@'%' IDENTIFIED BY 'secret';
mysql> flush privileges;
and end up with an empty database (obviously ;-)
I then create an SSH-tunnel (port 33006) on my client-machine to the mysql port on the mysql server and edit the first line of my config/Config.ini to read like:
When I do the same with my old moviemanger_entertainment and moviemanger_work databases, everything works fine. I can create and edit entries and I get no error traces when starting MovieManager from the command line. The new database moviemanager_test however leads to MovieManager tracing java errors.
ERROR net.sf.xmm.moviemanager.database.Database.getActiveAdditionalInfoFields(Database.java:548)
Exception:
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'moviemanager_test.Settings' doesn't exist
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
.... <snip> ...
ERROR net.sf.xmm.moviemanager.database.Database.getExtraInfoFieldNames(Database.java:931)
Exception:
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'moviemanager_test.Extra_Info' doesn't exist
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
... snip ...
....
So all of the functions
ERROR net.sf.xmm.moviemanager.database.Database.getActiveAdditionalInfoFields(Database.java:548)
at net.sf.xmm.moviemanager.database.Database.getActiveAdditionalInfoFields(Database.java:540)
ERROR net.sf.xmm.moviemanager.database.Database.getExtraInfoFieldNames(Database.java:931)
at net.sf.xmm.moviemanager.database.Database.getExtraInfoFieldNames(Database.java:922)
at net.sf.xmm.moviemanager.database.Database.getActiveAdditionalInfoFields(Database.java:560)
ERROR net.sf.xmm.moviemanager.database.Database.getListsColumnNames(Database.java:882)
at net.sf.xmm.moviemanager.database.Database.getListsColumnNames(Database.java:873)
ERROR net.sf.xmm.moviemanager.database.Database.getMoviesList(Database.java:3413)
at net.sf.xmm.moviemanager.database.Database.getMoviesList(Database.java:3373)
ERROR net.sf.xmm.moviemanager.database.DatabaseMySQL.getEpisodeList(DatabaseMySQL.java:1523)
at net.sf.xmm.moviemanager.database.DatabaseMySQL.getEpisodeList(DatabaseMySQL.java:1508)
at net.sf.xmm.moviemanager.database.Database.getEpisodeList(Database.java:3513)
ERROR net.sf.xmm.moviemanager.database.Database.getExtraInfoFieldNames(Database.java:931)
at net.sf.xmm.moviemanager.database.Database.getExtraInfoFieldNames(Database.java:922)
at net.sf.xmm.moviemanager.database.Database.getExtraInfoFieldNames(Database.java:907)
ERROR net.sf.xmm.moviemanager.database.DatabaseMySQL.addGeneralInfo(DatabaseMySQL.java:1090)
at net.sf.xmm.moviemanager.database.DatabaseMySQL.addGeneralInfo(DatabaseMySQL.java:1032)
ERROR net.sf.xmm.moviemanager.database.DatabaseMySQL.addGeneralInfo(DatabaseMySQL.java:1090)
at net.sf.xmm.moviemanager.database.DatabaseMySQL.addGeneralInfo(DatabaseMySQL.java:1032)
throw errors. I can fix the new database as described by mysqldumping -no-data and sourcing an already existing database into moviemanager_test.
But could this have something to do with me going over an ssh-tunnel rather than the new/old version thingie? I'll try to do a test database on my local machine.
Thanks and stay tuned.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
AFTER you have created the mysql database with the documented MySQL commands it is not enough to File/Open the database. You need to initialize it via the File/New dialog in MovieManager. Bro, could you patch MovieManager, that it does so automatically, when encountering empty databases in Config.ini resp. File/Open?
Short term it might be helpful to modify the documentation:
"Now you should be able to connect to the database. The first time you access this database you need to open it with the File/Open dialog in MovieManager for initialisation, after this you will be able to connet to it using the File/Open Dialog.
Hi all,
it seems, that creating new mysql databases is currently broken (2.9.1.), as there are no tables created in the procedure described on
http://xmm.sourceforge.net/index.php?menu=help#MySQL
Moviemanager itself seems to be unable to recognize missing tables + create them and consequently spews some errors + scary java backtraces of the kind
on startup
You can try to create a new entry when running MovieManager with this new database, but saving will just delete all field data and not save any new entries.
Workaround:
Have some old Moviemanager-database sitting around or download some very old version of MovieManager and create one + fill it with at least one entry, then do a
You can now use the file moviemanager_database.template.sql file to create the necessary tables by sourcing it into any new database you create (yes, I'm using several ;-).
Anyhow, thanks alot for this great program :D
Hi
I just tested on Ubuntu with MySQL 5.1.41, and latest version of MeD's Movie Manager, and it worked.
It's really strange that it works for you on an older version and not the latest. Have you tried to create the database using the root user?
Could you post the content of the log file from where the database is created?
Bro
Bro
Strange indeed. I'm running OpenSUSE 11.3 on both mysql-Server and MovieManager-clients (MySQL 5.1.46). I'm sorry, but there is no logfile, at least I can't find one ;-)
What I did serverside was the sequence:
and end up with an empty database (obviously ;-)
I then create an SSH-tunnel (port 33006) on my client-machine to the mysql port on the mysql server and edit the first line of my config/Config.ini to read like:
When I do the same with my old moviemanger_entertainment and moviemanger_work databases, everything works fine. I can create and edit entries and I get no error traces when starting MovieManager from the command line. The new database moviemanager_test however leads to MovieManager tracing java errors.
So all of the functions
throw errors. I can fix the new database as described by mysqldumping -no-data and sourcing an already existing database into moviemanager_test.
But could this have something to do with me going over an ssh-tunnel rather than the new/old version thingie? I'll try to do a test database on my local machine.
Thanks and stay tuned.
Ok, no difference when using a local mysql installation (first line of Config.ini file now reading:
I still get the aforementioned error traces. Weird. Something must be different in our java environments I guess.
I'm using
I'm out of ideas right now.
All the best, Felix
Hi again. I found some Log.txt file in the MovieManager dir, which seems to be the one you ar interested at.
I'll quote it as code.
Hope this is hopeful in any way, Felix
Problem identified:
AFTER you have created the mysql database with the documented MySQL commands it is not enough to File/Open the database. You need to initialize it via the File/New dialog in MovieManager. Bro, could you patch MovieManager, that it does so automatically, when encountering empty databases in Config.ini resp. File/Open?
Short term it might be helpful to modify the documentation:
"Now you should be able to connect to the database. The first time you access this database you need to open it with the File/Open dialog in MovieManager for initialisation, after this you will be able to connet to it using the File/Open Dialog.
in
http://xmm.sourceforge.net/index.php?menu=help#MySQL