Re: How to deal with sql-database structures on upgrade

2003-12-21 Thread Matthew Palmer
Marc Haber said: > On Mon, 15 Dec 2003 23:05:12 +0100, Thorsten Sauter > <[EMAIL PROTECTED]> wrote: >>Cacti use a mysql database to store the configuration values (including >>users/password, graphic options, layouts, ...). The new upstream >>version (0.8.x) use a completly new designed database st

Re: How to deal with sql-database structures on upgrade

2003-12-21 Thread Matthew Palmer
Marc Haber said: > On Mon, 15 Dec 2003 23:05:12 +0100, Thorsten Sauter > <[EMAIL PROTECTED]> wrote: >>Cacti use a mysql database to store the configuration values (including >>users/password, graphic options, layouts, ...). The new upstream >>version (0.8.x) use a completly new designed database st

Re: How to deal with sql-database structures on upgrade

2003-12-20 Thread Marc Haber
On Mon, 15 Dec 2003 23:05:12 +0100, Thorsten Sauter <[EMAIL PROTECTED]> wrote: >Cacti use a mysql database to store the configuration values (including >users/password, graphic options, layouts, ...). The new upstream version >(0.8.x) use a completly new designed database structure then the old >ve

Re: How to deal with sql-database structures on upgrade

2003-12-20 Thread Marc Haber
On Mon, 15 Dec 2003 23:05:12 +0100, Thorsten Sauter <[EMAIL PROTECTED]> wrote: >Cacti use a mysql database to store the configuration values (including >users/password, graphic options, layouts, ...). The new upstream version >(0.8.x) use a completly new designed database structure then the old >ve

Re: How to deal with sql-database structures on upgrade

2003-12-15 Thread Matt Zimmerman
On Mon, Dec 15, 2003 at 11:05:12PM +0100, Thorsten Sauter wrote: > > I'm going to adopt cacti[1]. But I have a problems with a clean upgrade > path to the new upstream version. > > Cacti use a mysql database to store the configuration values (including > users/password, graphic options, layouts,

Re: How to deal with sql-database structures on upgrade

2003-12-15 Thread Leo \"Costela\" Antunes
On Seg, 2003-12-15 at 20:05, Thorsten Sauter wrote: > Hi all, Hi > I have tried to write some postinst scripts to migrate the existing > database into the new one, but I think now this is impossible, because > maybe informations which are needed in the new version are missing in > the old one. >

Re: How to deal with sql-database structures on upgrade

2003-12-15 Thread Matt Zimmerman
On Mon, Dec 15, 2003 at 11:05:12PM +0100, Thorsten Sauter wrote: > > I'm going to adopt cacti[1]. But I have a problems with a clean upgrade > path to the new upstream version. > > Cacti use a mysql database to store the configuration values (including > users/password, graphic options, layouts,

Re: How to deal with sql-database structures on upgrade

2003-12-15 Thread Leo \"Costela\" Antunes
On Seg, 2003-12-15 at 20:05, Thorsten Sauter wrote: > Hi all, Hi > I have tried to write some postinst scripts to migrate the existing > database into the new one, but I think now this is impossible, because > maybe informations which are needed in the new version are missing in > the old one. >

Re: How to deal with sql-database structures on upgrade

2003-12-15 Thread Joerg Jaspert
Thorsten Sauter <[EMAIL PROTECTED]> writes: > Some other packages like sysstat simply prints a message about a > incompatible dataformat, and move or delete the old datafile. Is this an > acceptable way for such a program also? And if so, should I do a > database export first, before deleting and

Re: How to deal with sql-database structures on upgrade

2003-12-15 Thread Joerg Jaspert
Thorsten Sauter <[EMAIL PROTECTED]> writes: > Some other packages like sysstat simply prints a message about a > incompatible dataformat, and move or delete the old datafile. Is this an > acceptable way for such a program also? And if so, should I do a > database export first, before deleting and