Comment 2 for bug 1081551

Thanks for information :-)
Eva

On 7 March 2013 23:04, Lebbeous Fogle-Weekley
<email address hidden> wrote:
> Hello Eva.
>
> This bug has been reported at other sites, too. A technical note
> follows to guide the development of a future patch.
>
> serial.unit is a child table of asset.copy. Each table has a unique
> constraint for the "barcode" field (when the "deleted" field is false,
> anyway). These constraints do not prevent the duplicates between two
> rows if one row is only in asset.copy and the other is in serial.unit,
> due to a PostgreSQL limitation that I didn't appreciate when I wrote the
> serials batch receive code.
>
> The "safest" fix, from the point of view of providing the best guarantee
> of future data integrity, may be a trigger on INSERT or UPDATE
> operations to serial.unit that tests for the presence of the incoming
> barcode explicitly, and raises an exception when found.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1081551
>
> Title:
> No error message when using duplicate barcodes in Serials Batch
> receive interface
>
> Status in Evergreen - Open ILS:
> Triaged
>
> Bug description:
> Usually when duplicate barcode is used adding new item in Evergreen (e.g.. in Holding maintenance interface), we get an error message.
> But when we accidentally used duplicate barcodes for serial items in Serials Batch receive interface (we barcode each serial item individually) no error message appeared and we discovered the problem of coliding barcodes when checking out serial item in question,
> see http://knihovna.jabok.cz/Evergreen/bugs/duplicate_barcode.jpg
> I think there should be error message in Evergreen for using duplicate barcode in Serials batch receive interface too.
> We use Evergreen version 2.2
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/evergreen/+bug/1081551/+subscriptions