the app that I'm working on has some constraints that are implemented
under mod_perl , php & python.
i'm trying to figure out how to do this in pylons/sa -- hoping some
people can point me in the right direction
basically, I use 5 database connections -- each with different
permissions / roles
- config
readonly from main db on startup, populates a class with db
constants... the connection is not needed after initial loading.
- readonly
only reads from main db, active for every request
- write
writeable to main db , active on certain requests
- logger
does quick begin->log->end on visit metrics
- session
read/write on session-db for user persistance
sometimes these have the same db credentials... but i always abstract
stuff like this at the beginning so i can scale & not worry about
permissions
i usually accomplish this via a db factory class that returns a
connection, and has a request-start + request-cleanup hook for
transactional issues.
is anyone else doing something similar? if so, how have you laid this
all out? i'm trying to wrap my head around the layout of pylons.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to pylons-discuss@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
