That, and the fact that PostgreSQL is ACID-compliant (like SQLite), while MySQL doesn't have transactions, triggers and procedures unless you switch from the MyISAM to the InnoDB database structure.
For single-user solutions, I prefer the convenience and power of SQLite; and when I need a multi-user solution, I'll happily go for PostgreSQL and its enterprise strength. Jan Schenkel. ===== Quartam Reports & PDF Library for Revolution <http://www.quartam.com> ===== "As we grow older, we grow both wiser and more foolish at the same time." (La Rochefoucauld) --- On Tue, 6/9/09, Andre Garzia <an...@andregarzia.com> wrote: > From: Andre Garzia <an...@andregarzia.com> > Subject: Re: Remote database access: How? > To: "How to use Revolution" <use-revolution@lists.runrev.com> > Date: Tuesday, June 9, 2009, 12:33 PM > That kind of thing is exactly why I > recommend postgreSQL to everyone... > > -- > http://www.andregarzia.com All We Do Is Code. > _______________________________________________ > use-revolution mailing list > use-revolution@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage > your subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution > _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
