- Thread starter
- #11
rtv said:This might be because idActor isn't unique. To fix your db try this
Re actorinfo_idActor, actorinfomovies_idActor
Hmmm yer I forgot I filled these 2 tables with dummy data during the intial migration of my myth db so the later looked unique - doh!
That said I agree actorinfomoves_idActor is clearly not UNIQUE, but actorinfo_idActor does look like it should be UNIQUE to me? and looks like it could just be merged into the actor table. I've now removed both those indexes from the Original Post as I cannot see them being used much, cheers for the pointer.