On Mon, Sep 5, 2011 at 7:38 PM, Erick Erickson <erickerick...@gmail.com> wrote: [...] > You might be able to do something with creating a synthetic <uniqueKey> that > was the timestamp or some such, although be sure you don't generate > the same timestamp for two successive records, but I'm guessing. [...]
Which database are you using? Many of them offer an MD5, or similar, function that can be used to make a hash of some text that is likely to be unique from record to record. This should serve as a unique key. Regards, Gora
