[mythtv-users] Using same database with trunk and release

[Brian L. Walter]

Chad wrote:
> On 5/4/07, John Overchuk <overchuk at hotmail.com> wrote:
>   
>> If I have a database that was created and used with the latest trunk builds,
>> any thoughts on how well it would work if I tried to use the release version
>> of myth with it?
>>
>> _______________________________________________
>>     
>
> Depends.  I "accidently" did that a while back while testing out the
> -vid branch (without realizing it was going to change my db) and
> haven't had many issues since, and shortly after I tested the -vid
> branch I reverted back to .20-fixes and have been running it for quite
> some time.  I do have a few hiccups occasionally and I do blame my
> lack of backup-prior-to-db-change for the hiccups, but it wasn't like
> I had to wipe the slate clean and start over.
>
> The other side of the that depends is that it was quite a while ago
> and .20-fixes and -vid weren't that different of db schemas (it was
> shortly after the .20 release) while today an SVN schema and a
> .20-fixes schema may be entirely incompatible.
>
> -Chad
>   
I've had pretty much the same experience.  It looks like, from the code, 
that selects etc are done via direct column names.  If thats true, I 
doubt that colums got *dropped* in updates, so the net would be that you 
have more information in the database than you are actually using.

And it doesn't appear that Myth uses things like stored procedures or 
triggers (I didn't see any stored procedures defined in the schema...not 
sure about triggers), so, it might work, and as mentioned above, you 
might have a few hiccups.

I've gone from 0.21 back to 0.20 rpm to 0.20-svn back to 0.20 rpm (which 
is now 0.20.1), and the only things that I have issues with are 
ff/rewind and closed captions.  However, FF/rewind broke when I went to 
trunk, so not sure if it's related.

Brian