: koha-devel
Subject: Re: [Koha-devel] Alerting users to breaking changes / backwards
incompatibility
Create an SQL report with the following query:
SELECT COUNT(marcxml) FROM biblioitems;
And then go to the reports list. You will notice it tells you this:
https://snipboard.io
> 72/330 Wattle St
>
> Ultimo, NSW 2007
>
> Australia
>
>
>
> Office: 02 9212 0899
>
> Online: 02 8005 0595
>
>
>
> *From:* Tomas Cohen Arazi
> *Sent:* Thursday, 28 May 2020 9:53 AM
> *To:* David Cook
> *Cc:* koha-devel
> *Subject:* Re: [
0 9:53 AM
> *To:* David Cook
> *Cc:* koha-devel
> *Subject:* Re: [Koha-devel] Alerting users to breaking changes /
> backwards incompatibility
>
>
>
> We already do something similar with the biblio_metadata table.
>
>
>
> El mié., 27 de mayo de 2020 20:35, e
: [Koha-devel] Alerting users to breaking changes / backwards
incompatibility
We already do something similar with the biblio_metadata table.
El mié., 27 de mayo de 2020 20:35, mailto:dc...@prosentient.com.au> > escribió:
Hi all,
I was just thinking how a lot of SQL reports will
We already do something similar with the biblio_metadata table.
El mié., 27 de mayo de 2020 20:35, escribió:
> Hi all,
>
>
>
> I was just thinking how a lot of SQL reports will return unexpected
> results when we merge the deleted* tables with their live/active
> counterparts.
>
>
>
> What do
Hi all,
I was just thinking how a lot of SQL reports will return unexpected results
when we merge the deleted* tables with their live/active counterparts.
What do people think about a modal popup in the reports (on a per user
basis) alerting them to how they may need to update their
