I have just setup a clean RC1 TV Server and found that Foreign Key Contraints have not been created. I was using an existing SQL Server installation which as never had the TVLibary database before. Is this a bug or did sometime go wrong during the installation?
Foreign Key Constraints missing with RC1 (1 Viewer)
- Thread starter dsnaith
- Start date
Germany
They've been left out because they're not honoured manually by MP's code (as a result of MySQL's MyISAM DB backend not supporting foreign keys).
Did you stumble upon any errors because of this?
(Usually plugins should be robust for that - e.g. Exceptions because of mapped channels which have been deleted must be caught).
Did you stumble upon any errors because of this?
(Usually plugins should be robust for that - e.g. Exceptions because of mapped channels which have been deleted must be caught).
- Thread starter
- #3
Why MyIsam
As ISAM is a very old database engine and MySQL supports other engines which do have "foreign key constraints" and SQL Server support "foreign key constraints", why take them out.
I notice the constraints where missing only when I queried the database directly and have seen them there in the SVN builds. To assume that programs will do the right thing is not the safest approach. I work with databases all day and have seen corrupted data many times due to lack of constraints. This also makes life harder when working on plugins etc as they can aid the developers understanding of the database.
I'm new to Media Portal but I'm impress so far, it would be a shame if something as simple as lack of constraints was to spoil the product.
As ISAM is a very old database engine and MySQL supports other engines which do have "foreign key constraints" and SQL Server support "foreign key constraints", why take them out.
I notice the constraints where missing only when I queried the database directly and have seen them there in the SVN builds. To assume that programs will do the right thing is not the safest approach. I work with databases all day and have seen corrupted data many times due to lack of constraints. This also makes life harder when working on plugins etc as they can aid the developers understanding of the database.
I'm new to Media Portal but I'm impress so far, it would be a shame if something as simple as lack of constraints was to spoil the product.
Be assured it does not.. Oh - and you maybe want to switch the backend to InnoDB or something else - it's up to you. Although it fits the tasks just well and every other backend will be slower with MP 