Not having duplicates in Azure Tables?


  • If I have one object, 'Student', which will be associated with 2 'Course' objects, I think I need to add the student to azure tables first with a partitionkey of 'Class1_Student1', and then again with 'Class2_Student1'.

    My understanding is that I would then have duplicate student objects, just with different partitionkeys.

    What I would like is to add a Student and point it to multiple classes, where if I ask for that student I get the same object.  Or a way to check before adding if this student exists and if so reuse the existing object.

    What's the best way to accomplish this?  Or does needing this functionality suggest I should be looking towards SQL Azure?

    Tuesday, June 26, 2012 11:00 PM