On Thu, Sep 10, 2009 at 9:19 AM, Jules Stevenson <[email protected]> wrote: > >> Is there some reason you can't connect to the database remotely? >> That's the most efficient way. > > Hi Mike, > > Yes, I've kind of found that trying to do stuff through JSON is not really > going to hack it. As it's an Intranet I'm currently installing sqlalchemy > and importing a slightly modifed model on each client machine and connecting > directly to the DB over the local network (it's an SQlite db) by changing > the bind to create_engine. However (and this may be wrong / a stupid > question) does doing it this way have issues with concurrent access to the > DB? I.e is it pylons / paste server that keeps everything thread safe, or > sql alchemy [and therefore ok to do this]? Apologies if I've used the wrong > terminology, learning as I go :).
MySQL and PostgreSQL will definitely work for remote access. I wouldn't recommend SQLite for it. Accessing it via a network drive is disrecommended ( http://sqlite.org/whentouse.html, section "Client/server applications"). In the case of a central Pylons website, Pylons is converting remote web requests to local database queries, so it's not remote database access per se. -- Mike Orr <[email protected]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
