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
stacks/files...
All options are possible, some require a bit more scriptign though ;)
Cheers
Xavier
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Oak Norton
Sent: Friday, April 15, 2005 20:15
To: 'How to use Revolution'
Subject: 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
Chipp Walters at Altuit has a really elegant solution to this problem.
I'm sure he'll jump in when he visits the list next.
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
version or
not. I find that most convenient.
Cheers
Xavier
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 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
Hi Oak,
As I mentioned previously, SQLite is perfect for this type of project.
It is virtually a zero-free maintenance database and updating it is as
simple as updating the connector/engine file (1 file)- though it
shouldn't need updating.
Our demo stack automatically checks to see if you have
