Comment 3 for bug 1869896

Postgres has an included module called citext that may be useful if we move forward with this.
https://www.postgresql.org/docs/13/citext.html

But I think that would make it a non optional features.

I found a few patron barcodes that were conflicting, but they are all examples of situations that shouldn't be allowed anyway, or work arounds.

No copy barcodes in our system that differ only in case.

On my 3.11.0 test system there are two index entries for actor.card(barcode).

    "actor_card_barcode_evergreen_lowercase_idx" btree (lowercase(barcode))
    "card_barcode_key" UNIQUE CONSTRAINT, btree (barcode)

We have added student cards recently, that use a school district alpha prefix, so it is a bit of a pain that students need to always enter the prefix in caps for it to work.

ABCD4567 not being equal to abcd4567.

Josh