Hi Raoul,
You are right that there are no explicit primary key definitions right now, primarily because miRMaid is "read-only" at the moment and this was therefore not a major concern for the first iteration.
However, there should be indexes for most important joins and look ups right now. It would be great though, to convert the appropriate indexes to primary key definitions. Maybe you work could could end up with a new version of the "001_mirbase_to_mirmaid.rake" script in db/migrate?
In the case of matures_seed_families, it is supposed to be a "transparent" many-many relation between matures and seed_families. A composite primary key is therefore not needed here, I think. Instead we have isolated indexes on the 'mature_id' and 'seed_family_id' columns to optimize joins from the matures and seed_families tables.
In the situation you are referring to
57154;12639;2
-Anders