On 11/09/2010 09:59 AM, Alvaro Herrera wrote:
And this makes me think that SQLite is indeed the right tool for the job here, and not PostgreSQL. If someone intrudes, it's going to be in the same process running the web browser, not in some server running under another user identity in the machine. That seems like a feature to me, not a bug.
Right. Then it has some chance to be run in a sandbox. This doesn't strike me at all as a good fit for Postgres.
cheers andrew -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
