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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
