Offtopic: To Check or Not to check for duplication. (DBDatastores)

Hey Steve!

Yea I fully utilise getOrInsert. It works okay. The above scenario is not really about Datastore handling but After I do receive those DBRecords. In essence its about handling duplication locally. I don't use LocalDatastores.

Heres what I do.
I have a local db where I store recordID and the text. ( yes i don't use localDatastores, aah, for some reasons).

For Incoming DBRecord: (At Sync)

1. I check if recordID already exists, if yes, I update the localDb.record.text = record[@"text"]. If it does not exist, I create a New row in my localDB with that recordID and text. This is fine. The uniqueness of a DBRecord is the record["text"]; thats it.

I save the recordID and text field on the localDB.

Ok great.

Now, I open up This very same DBRecord. I want to update the text of this very DBRecord. I don't want to create a new one. I want to update this DBRecord. I already know its recordID, because I stored it on my localDB.

I get that DBRecord using getOrInsert, and I update the record["text1"] field (text --> text1). And sure enough the record is updated with new data. BUT, it is here that the relationship between recordID and the text field has become invalid. When this DBRecord was created`, the recordID == md5("text"). NOW: md5("text1") != recordID.

Next time, When I create a new record with text1 (like importing from the same file) that is equal to the text1 from above; I potentially created a duplicate DBRecord.

• I know that text1 exists already in a DBRecord.
• But I cannot avoid duplication by looking for md5(text1).
• that DBRecord has an Older md5(text), but text was later updated to text1.

I want to be able to give my self a choice to avoid this kind of duplication. What would you guys do here?

Its way early morning right now. I hope what i wrote is understandable. This isn't a datastore problem. Its my problem :/