Re: [Streamline-User] Upgrade to cvs / playlists

[Michael M. <mi...@ma...>]

Henk,

The 1.0 Beta 4 Version will upgrade from Beta 3 (In Theory).  I haven't 
written any docs yet on how to actually do the upgrade.  In short this 
is how it would be done.

1)  Take your current installation of streamline and move it (just 
rename the dir to something like streamline-old.)
2)  Upack (or otherwise install) the latest version.
3)  Run the web installer for beta 4 just like you did for beta 3.  This 
time it will ask you if you want to install, repair or upgrade.  Choose 
upgrade and follow the prompts.

Basically what is going on is the database schema gets updated and new 
values are added.  I would strongly suggest making a back up of your 
database before doing this since it hasn't been really tested a lot 
yet.  I know that at some point I have done the upgrade on mysql, 
postgresql, and sqlite and it worked on all three, but I haven't tested 
it in a while.

This is one way to do the upgrade.  To make CVS usage easier for the 
versions coming after beta 4, they will be able to tell when the schema 
needs to be updated and kick of the upgrade for you.  Most end users 
dealing with tar balls will have to follow the procedure above.

I am surprised that a clean install doesn't work, I  know it works with 
mysql and sqlite.  I will test it tonite with postgresql and if there 
are any problems I will fix them tonite.

As for the playlist issue, you are correct when you try to edit a 
playlist you really have to save it as a different name.  The fix for 
this is a little complicated it.  I think it should work like this:

1)  Load a play list.
2)  Edit that list.
3)  Choose save.
4)  The save dialog comes up with the name of the loaded list already in 
the box.
5)  The user can either change the name or save it.
6)  Maybe they should be prompted to confirm replacing the existing list.
7)  If they confirm, the entries for the old list are removed and the 
new ones are added.


Do do this a couple things need to change I think.  For one the system 
has to remember the name of the currently loaded list.  Also a 
confirmation step for replacing a list with the same name needs to be 
made.  Lastly it seems like this scenario would also apply if you just 
made a new list and then save it with the name o an existing list (Since 
this is basically what is happening here, the only difference being that 
the list name is automatically populated in the save dialog).

What do you think?  I am open to discussion on this.  I hardly use the 
playlists so I am interested to hear what you other users think.  Thanks.

~Mike

Henk van Lingen wrote:

>Hi Michael,
>
>2 questions:
>
>-- Should it be possible to upgrade from beta3 to current cvs? I tried
>   yesterday and was't straitforward (I tried to keep the database).
>   A clean install also didn't work. I noticed you commited something
>   today. Do you have some hints on the current status and the prefered
>   way to use cvs without whiping your base each time?
>
>-- There seems to be an issue with saving playlist with the same name,
>   i.e. when you want to edit an existing playlist (double entries
>   in the database). Has this changed since beta3 or should I have a
>   look at it?
>
>Cheers,
>  
>