I inherited a database constructed with the concept that composite secrets tend to be better than utilizing a unique object ID area which when creating a database, just one unique ID should never be utilized for a principal key. Because I had been creating a Rails from finish with this database, I went into difficulties setting it up to adapt towards the Rails conventions (although it was possible using custom sights along with a couple of additional gems to deal with composite secrets).
The reasoning behind this unique schema design from the one who authored it had related to the way the database handles ID fields inside a non-joyful manner so when it's building indexes, tree sorts are problematic. This explanation didn't have any depth and I am still attempting to wrap my mind round the concept (I am acquainted with using composite secrets, although not 100% of times).
Can anybody offer opinions or add any greater depth for this subject?