[Koha-bugs] [Bug 20271] Merge deleted biblio, biblioitems, biblio_metadata, and items tables

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20271

--- Comment #228 from Tomás Cohen Arazi <tomascohen at gmail.com> ---
(In reply to Katrin Fischer from comment #227)
> (In reply to Tomás Cohen Arazi from comment #226)
> > (In reply to Jonathan Druart from comment #225)
> > > Tomas, with your patches we now have:
> > >   biblio.deleted_on, biblio.deleted
> > > and
> > >   items.deleted_on, items.is_current
> > > I think it's confusing.
> > 
> > Yes. I think is_current is an anomaly and shouldn't be the rule. But I
> > wouldn't block this for that.
> 
> Can you explain? I think if possible we should be consistent, thinking of
> the many report writeres out there.

Comment #198 explains it. What really makes sense is a 'deleted' flag, but
because of this very special case in which we want to preserve the UNIQUE
constraint on the items.barcode column which some libraries would like to
reuse, and the DBMS doesn't allow us to have the constraint on non-NULL values,
we need to do it in reverse (i.e. instead of 'deleted' we do 'not_deleted' and
set NULL to represent deleted). So we are forcing the DB structure because of
our limitations on the DB features we are allowed to use, or the versions of
the DB we want to support (all for good reasons, not arguing).
I would just add a FIXME on the items table and leave the other tables saner.

-- 
You are receiving this mail because:
You are watching all bug changes.