If you are going to implement real security, it shouldn't matter if
someone nows the "unique id" of a record. You should be checking if
they have the right to see that record.
But regardless, there is an easy way to set random ids as your
"unique" identifier. Setup 2 fields, one being the r
On 8/7/07, Boyd Hemphill <[EMAIL PROTECTED]> wrote:
>
> Suggestions to use a hash are a problem because once you have a few
> million rows the likelihood of a collision is quite high if you cannot
> afford an error stopping your application. This means that if you write a
> trigger (the obvious wa
