On 02/18/2015 08:36 PM, Ben Finney wrote:
memilanuk <memila...@gmail.com> writes:
They would need to be able to set up the application (and whatever
database) on their laptop or PC, wherever that may be, and spend their
time administering the event, not the database engine.
So, the database will only be accessed by exactly one application, on
exactly the same machine and storage as the application? If so, you
don't need concurrency.
Otherwise, your database needs concurrency; and the person installing
the database will need to make a lot of decisions about the specific
network environment and devices to be allowed to access the database.
But is this what you mean by your requirements not being met by SQLite?
In the past I've been waffling back and forth between a desktop
client/server setup, or a web-based interface with everything on one
computer. At this point I'm leaning toward the latter.
--
Shiny! Let's be bad guys.
Reach me @ memilanuk (at) gmail dot com
--
https://mail.python.org/mailman/listinfo/python-list
