Hi all, long time no lift,
I want to verify that I'm not crazy re: mapper functionality and then move into another discussion:
1. Is it not possible to use a MappedLongForeignKey (in Mapper) with a unique index?
I use the negative in that question, because
it looks like adding a `dbIndexes` UniqueIndex (which I believe is the proper way to do this) will attempt to create an index twice (one for the `mappedFields` calculation and one for the `table.dbIndexes` loop). This will explode since the index already exists. Is there another way to do this or would this involve rolling my own?
2. Assuming the answer to the above is that it's not possible, I'm curious to know what the suggested ORM to use is these days.
It seems like Mapper vs Record is the conversation, but from what I see neither are fully robust. Having a unique foreign key seems pretty standard to me, and it makes me a little nervous moving forward with a corporate project with something that seems to lack what I think are "the basics."
Not tryin to pick a fight, but curious to hear opinions of the masses.
thanks all