Handling updates

[MisterX]

i might add the phpnuke method...

when you decide to upgrade

a php sql web page (compared to a stack script) updates first your
database structure and injects or deletes the data so it's ready for
the next version... It's quite handy. In my case, where I can't reach
my php server via rev sql calls, I use phpmyadmin as intermidiary.

Copy paste though... But Rev generate the sql quite quickly and 
puts it in my clipbaord in one click... so it's a no brainer for
lame cases like mine...

Should it be constant, i'd use the phpnuke method... and incremental or
alternative set of objects for each subsequent version (where different
clients have different versions). With incremental objects you can downgrade
if something goes wrong. 

Storage might be an issue though. And you might not want to trade that for
the possibility to downgrade later...

Another possibility is to ensure that outdated clients should update when
they dont match the sql data to engine/structure version...

I read across the lines but I dont think im way off the line... For my
stacks i just use a simple text file with a text table... no need for
anything complicated... This tells the user he has the latest version or
not. I find that most convenient.

Cheers
Xavier

> -----Original Message-----
> From: use-revolution-bounces at lists.runrev.com 
> [mailto:use-revolution-bounces at lists.runrev.com] On Behalf Of 
> Frank D. Engel, Jr.
> Sent: Friday, April 15, 2005 20:57
> To: How to use Revolution
> Subject: Re: Handling updates
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> This is more a matter for the people behind the database 
> server you choose.
> 
> I know for PostgreSQL, however, that a single database may 
> consist of many files with names which may not be extremely 
> obvious.  The files may not be compatible with future 
> versions of the database engine, so if updating the database, 
> you may need to backup the database before starting (dump 
> it), then restore it after the upgrade.
> 
> Additionally, with any database server like this, you should 
> *never* try to access the files directly while the server is 
> (or might be) running, due to the possibility of corrupted data.
> 
> 
> On Apr 15, 2005, at 2:14 PM, Oak Norton wrote:
> 
> > OK, another newbie question.  Once you install a program on 
> someone's 
> > local machine for win/linux/mac that uses mysql or PG, do you 
> > typically notify them of patches to the engine or expect 
> end users to 
> > be smart enough to go out and get the patches themselves?  
> It doesn't 
> > seem likely that most end users would have any clue how to 
> do this.  
> > So if I have a robust application that uses one of these databases, 
> > are people required to patch, or since it's a local install can you 
> > just toss a database file out there that will respond to 
> sql queries 
> > like an access database where it's essentially just a file? 
> (I don't 
> > suppose there's a hack to let access databases run on
> > Mac/Linux???)
> >
> > Thanks,
> >
> > Oak
> >
> > _______________________________________________
> > use-revolution mailing list
> > use-revolution at lists.runrev.com
> > http://lists.runrev.com/mailman/listinfo/use-revolution
> >
> >
> - -----------------------------------------------------------
> Frank D. Engel, Jr.  <fde101 at fjrhome.net>
> 
> $ ln -s /usr/share/kjvbible /usr/manual
> $ true | cat /usr/manual | grep "John 3:16"
> John 3:16 For God so loved the world, that he gave his only 
> begotten Son, that whosoever believeth in him should not 
> perish, but have everlasting life.
> $
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (Darwin)
> 
> iD8DBQFCYA5w7aqtWrR9cZoRAg8pAJsE0ADREJbDMpO0zMDku8T2/zwwRACcDt8A
> cdzEDdOjg40sgXcqj0eM8ZQ=
> =PHMz
> -----END PGP SIGNATURE-----
> 
> 
> 
> ___________________________________________________________
> $0 Web Hosting with up to 200MB web space, 1000 MB Transfer 
> 10 Personalized POP and Web E-mail Accounts, and much more.
> Signup at www.doteasy.com
> 
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>