Reply to thread

Message

<blockquote data-quote="Anthony Vaughan" data-source="post: 1253450" data-attributes="member: 153283">Hi CyberSimianOkay, I think I have worked it out. In the VideoDatabaseV5.db3 SQLite database there is a table called 'path' that has a column called 'cdlabel'. If this column is empty for non-film program, MP seems to ignore it and created a duplicate record. When the 'cdlabel' contains 'unknown', then MP does not create a duplicate record nad uses the existing record to generate file and movie records.How, you may ask, could the cdlabel column be null. Well, I have developed a system that synchronizes VideoDatabaseV5.db3 changes for all clients in my MP setup. VideoDatabaseV5.db3 is a single user database and I have to make the MP system multi-user. I do this by saving all changes to any of the client VideoDatabaseV5.db3 files in a separate - common to all clients - database and then apply those changes to each of the client VideoDatabaseV5.db3 files when the system is idle. I have also allowed a new VideoDatabaseV5.db3 database file to be created based on an existing common synchronized database. Since I was unaware of the 'unknown' feature, I found the duplication issue. Of course, this is not a issue with MP, but a self-imposed problem.Anyway, all is now resolved.Tony</blockquote>

[QUOTE="Anthony Vaughan, post: 1253450, member: 153283"] Hi CyberSimian Okay, I think I have worked it out. In the VideoDatabaseV5.db3 SQLite database there is a table called 'path' that has a column called 'cdlabel'. If this column is empty for non-film program, MP seems to ignore it and created a duplicate record. When the 'cdlabel' contains 'unknown', then MP does not create a duplicate record nad uses the existing record to generate file and movie records. How, you may ask, could the cdlabel column be null. Well, I have developed a system that synchronizes VideoDatabaseV5.db3 changes for all clients in my MP setup. VideoDatabaseV5.db3 is a single user database and I have to make the MP system multi-user. I do this by saving all changes to any of the client VideoDatabaseV5.db3 files in a separate - common to all clients - database and then apply those changes to each of the client VideoDatabaseV5.db3 files when the system is idle. I have also allowed a new VideoDatabaseV5.db3 database file to be created based on an existing common synchronized database. Since I was unaware of the 'unknown' feature, I found the duplication issue. Of course, this is not a issue with MP, but a self-imposed problem. Anyway, all is now resolved. Tony [/QUOTE]

Verification