Take a look at my configure class in Blogitizor. It gives a class interface to a settings table, and will cache the results in ram, the only thing it misses is clearing out the cache when a setting changes
http://code.google.com/p/blogitizor/source/browse/src/modules/utils.py You can take a look in how its used in the models. -Thadeus On Tue, Feb 9, 2010 at 12:56 PM, Jonathan Lundell <jlund...@pobox.com> wrote: > I've got an application that makes very limited use of the database. No > self-registration, and the only other table is a relatively static > configuration table. So for convenience, I'd just as soon stick with SQLite > for simplicity and self-containedness. > > So two questions, I guess. > > 1. Would there be a problem with the auth tables? Logging, maybe? There could > be multiple users. > > 2. Is there a straightforward way to serialize access to my configuration > table? I'm not particularly concerned about performance. I can always use a > system semaphore, I suppose, but how about something in the web2py core, > since it's persistent? > > -- > You received this message because you are subscribed to the Google Groups > "web2py-users" group. > To post to this group, send email to web...@googlegroups.com. > To unsubscribe from this group, send email to > web2py+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/web2py?hl=en. > > -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
