On 28/02/2012 19:56, lars van gemerden wrote:
I can see that being true in the general case, and at some point i
will start working with a serious database, but at the moment i am
working on a prototype (in which db persistance is maybe a quarter of
the work), still have a long list of items to implement and was hoping
to abstract away from sql and database specifics with sqlalchemy.
Yeah, but SQLAlchemy can only offer what the database underneath it
provides. sqlite has some niches its very good at, but a general purpose
rdbms it is not.
If you don't want to worry about a database now, pick postgres and
reconsider later if you need to rather than having to spend so much time
now working around sqlite's limitations.
cheers,
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com.
To unsubscribe from this group, send email to
sqlalchemy+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en.
