[mythtv-users] why change db stuff with every version change?
myth at robinhill.me.uk
Wed Nov 25 09:11:11 UTC 2009
On Wed Nov 25, 2009 at 12:08:39AM -0800, Evuraan wrote:
> .22 frontends will not work with .21 backends
> This version of MythTV requires an updated database.(schema is 30
> versions behind)
> sounds too familiar, I had to tear down my db & rebuild when i came
> from previous versions to 0.21 and seems the cycle repeats again.
> which makes wonder, why are we doing this to ourselves?
Not sure what you mean - there's no need to "tear down the db" at all
(unless you've corrupted it previously). The backend/setup programs
will update the schema automatically to the new one (as did previous
> why cant we leave the db schema as it is?
Beacuse new functionality needs backend support. Extra tables are
required for storage groups for example.
> now if you have solid reasons to convince that changes in db schema
> with every version change is good evolution supported by good reasons,
> pls treat this as a silly rant.
> or at least, provide some sort of backward compatibiity so that the
> precious db of yester years continues to be of use with upstream
> versions w/o having to redo the db that'd be swell.
This is a major maintenance problem - backward compatibility requires a
huge amount of complicated logic, workarounds, etc. which will increase
the likelihood of issues.
What's preventing you updating all the backends/frontends anyway? It's
not like there's embedded systems which will need replacing at large
cost, it's just a software update.
( ' } | Robin Hill <myth at robinhill.me.uk> |
/ / ) | Little Jim says .... |
// !! | "He fallen in de water !!" |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 198 bytes
Desc: not available
More information about the mythtv-users