Thanks, Robert!

Thanks, Danny!

Actually, I raised already similar discussion but I still prefer object callbacks because of better code readability.

BTW, if I have both unified Trigger and OnBeforSave callback would they fire both?

And why don't we have unified ObjectScript callbacks?

Hi, Vitaly!

Thanks for your input! This is very interesting and totally different approach to solve the task which I like every time about InterSystems technology that problems can be solved with different approaches and you never know how many options even exist )

Hi!

Here is the remastered version of Meetup live stream recording.

So, the final recipe looks like following:

For Insert and Update calculate the hash e.g. with MD5 and put it in Hash property. Index it with not unique index.

Find duplicates with SQL query on Hash where group by for hash shows more than one occurrence.

Loop through all the values with same hash just and check Text property values to be sure that they are duplicates but not hash collisions.

Thanks, Alex, Dmitry, Robert!

True, but it can find also similar, but not identical, right? 

Hi, Robert!

Thanks! That's really nice!

Thanks, @Alexey Maslov! What is the preferred algorithm to use hashes in this case?

And what about collisions? Should I care about that too?

Thanks, Eduard. But I'm looking for duplicates, not for similar records. How can %SIMILARITY help here?

Thanks, Dmitry. Yes, the focus is - best performance.

But what about the index declaration? There is a limitation of 511 symbols in an index, right?

Should I put that in an index declaration or it will solve it for me automatically if I index an entry with value >511 symbols?