SVN updated also the database (structure)

[sunflower]

Hi, installing the SVN updated also the database (structure), previous data was lost. Three questions:

- Why is this done? What was changed in the db-structure (tables, columns)?
- I made a backup of the db before installing the SVN , can I use it?

- Would it be possible to describe the changes in the db-structure for new SVN's
as reconfiguring the entire database takes a lot of time (channel scan, grouping, renaming and mapping channels, web epg...)

[frodo]

Hi, installing the SVN updated also the database (structure), previous data was lost.

Yes this can happen if you use latest svns

- Why is this done? What was changed in the db-structure (tables, columns)?

Its done to add support for DVB-S2 by adding the pilot & rollof values
to the database

- I made a backup of the db before installing the SVN , can I use it?

no

- Would it be possible to describe the changes in the db-structure for new SVN's

Its possible, but not done atm. We only warn people about database changes
when a new release has been made.
Will discuss it with the team
Frodo

[vvulture]

I understand the risks with using SVN's, and most of us will take this risk...

But it would be nice if a warning was included when database changes are required, because it would make some of us wait before taking the plunge.

I decided to update to the latest SVN last night thinking that it would take no more than an hour or so...., but i was annoyed when i realised that it was now going to take a hell of a lot longer..

just my 2 cents worth..

[Nemulate]

If you use svn's then it's 'part and parcel' things may change! I've had to rescan/setup channels several times over lasr few months but just accept it as part of using 'beta' software! Spose morale is 'don't use svn if yu don't want change'

[Muldini]

Originally Posted by vvulture

I understand the risks with using SVN's, and most of us will take this risk...

But it would be nice if a warning was included when database changes are required, because it would make some of us wait before taking the plunge.

I decided to update to the latest SVN last night thinking that it would take no more than an hour or so...., but i was annoyed when i realised that it was now going to take a hell of a lot longer..

just my 2 cents worth..

After installing the new SVN, the Server tells you that the DB needs to be updated, you can cancel at this point and revert to your old SVN with the old setting still being there.

Regards,
Muldini

[vvulture]

Originally Posted by Nemulate

If you use svn's then it's 'part and parcel' things may change! I've had to rescan/setup channels several times over lasr few months but just accept it as part of using 'beta' software! Spose morale is 'don't use svn if yu don't want change'

Like i said... i understand the risks..

After installing the new SVN, the Server tells you that the DB needs to be updated, you can cancel at this point and revert to your old SVN with the old setting still being there.

Regards,
Muldini

Well actually, i was not warned that the database needed to be changed.
I was actually greeted with a message that told me that a database update had failed, and that a new database needed to be created.
It was already too late.
Not once was i aksed if i wanted to proceed with a database update..

[sunflower]

I can understand using SVNs is always risky and takes time.

My wish was just to know which changes had been made in the db.
With a bit of db knowledge one could change the db's structure manually (add fields etc) without detroying the entire db, or reload the untouched tables from a backup. This could save a lot of work.

[Muldini]

2 fields for DVB-S2 were added. ( http://forum.team-mediaportal.com/sh...8&postcount=10 )

Like frodo said, a change that makes it possible to keep the old data is currently being discussed by the team.

http://forum.team-mediaportal.com/im...ng-t25700.html

Regards,
Muldini

[vvulture]

Originally Posted by sunflower

I can understand using SVNs is always risky and takes time.

My wish was just to know which changes had been made in the db.
With a bit of db knowledge one could change the db's structure manually (add fields etc) without detroying the entire db, or reload the untouched tables from a backup. This could save a lot of work.

I second that... Its a good idea.

Like frodo said, a change that makes it possible to keep the old data is currently being discussed by the team.

http://forum.team-mediaportal.com/im...ng-t25700.html

Regards,
Muldini

Don't mean to be rude, but talk about an afterthought....

[joystick]

Hi folks,
I'm jsut a new user to MP, and I was wondering If you have to uninstall TV Server everytime you want to use the latest SVN, unlike with the client, where you can install SVN just "on top"
This is no thread "hijacking"- I just thought that my question fits the threat...
thx

cheers
joystick