Check attributes for consistency amongst key definitions

[AndyDentFree]

Because we're specifying the primary key using the attribute [PrimaryKey] [ObjectId]we need a check to make sure this is not specified on more than one field in a given class. This has to be a runtime check. Update 2016-02-19 with more Fody knowledge, now realise we can easily do this in Fody

Alternatively, we could redesign the feature to specify the primary key with key name as parameter and make it a class-level attribute. That would take care of the problem of specifying more than one but then add a different check to ensure the field name was valid and that the field wasn't tagged with the [Ignore]

[AndyDentFree]

https://github.com/realm/realm-wiki/wiki/Bindings says we should specify single or, possibly, multiple properties to act as a primary key so it seems multiple field specification is explicitly required - the problem then is one of ordering of fields to provide the composite key.

[bmunkholm]

multiple keys are not yet supported. But it doesn't harm to consider if the
API that get's made could support it.

On Sun, Aug 16, 2015 at 11:53 AM, Andy Dent notifications@github.com
wrote:

https://github.com/realm/realm-wiki/wiki/Bindings says we should specify
single or, possibly, multiple properties to act as a primary key so it
seems multiple field specification is explicitly required - the problem
then is one of ordering of fields to provide the composite key.

—
Reply to this email directly or view it on GitHub
#38 (comment).

[AndyDentFree]

Note that PrimaryKey was renamed ObjectId (we're at least floating with that in the dotnet betas and will see how users react, other products haven't changed).