×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Do you really need uniqueness in a transaction history field? Let's say
you are Walmart and you had two purchases of aspirin on 11/19/2010 at
11:10:25. So your item history file has two records at that same time.
Who cares? Now, there may be something in there that ties back to
transaction id so that you could tie it back to a register receipt or
online purchase. There's nothing actually to say that the same register
pumped through two bottles in the same second, and still be two records in
the item transaction history file.
Normally when you purge a transaction history file it's by a date range so
you aren't inhibited by lack of uniqueness. Now if your system is fubared
and you're goal is to remove a series of double entries from a programming
bug then that's more of a freak and stupid errors should make the
programmer work harder to back them out.
But, in summary, does a transaction history file really need a unique key?
If you do, then use UUID or GUID, an "SQL sequence" or whatever. STW for
more info on those. And then use a unique key constraint.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
