[mythtv] [mythtv-commits] Ticket #13261: Better solution for schema or protocol mismatch
Nigel Pearson
nigel at ind.tansu.com.au
Tue May 1 03:35:53 UTC 2018
> On 1 May 2018, at 4:45 am, Ian Campbell <ijc at hellion.org.uk> wrote:
>
> Perhaps in that spirit we could/should require both the build to have
> used the IGNORE_SCHEMA_VER_MISMATCH _and_ the runtime -O added here
> (i.e. the compile time option just adds a new default-off runtime
> option).
>
> That would reduce the risk of having such compiled binaries floating
> around since they would need to be manually "weaponsized" at runtime
> too, thus addressing "do not have to build with those dangerous
> options”.
Sure, we could add -O or another runtime enabler,
or could force UpgradeTVDatabaseSchema() and friends to alert the user?
From memory, I think the original intent of the IGNORE_ hack
was to allow _quick_ build/run/debug against a mismatched DB.
I think the automatic DB backup stuff was added just after this,
to make the “weapon” less dangerous.
--
Nigel Pearson, nigel at ind.tansu.com.au|"Your face looks like it was
Telstra Voice/Vid, Sydney, Australia | hit with a Prius. And your
Office: 8576 5449 Fax: 9298 9033 | Prius looks like it was hit
Mobile: 0408 664435 Home: 9792 6998 | with a telephone pole!”
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-dev/attachments/20180501/34da6d6f/attachment-0001.html>
More information about the mythtv-dev
mailing list