On 25/02/2012 11:07, lars van gemerden wrote:
Actually, now I think about it, i had a couple of reasons:
- easy to start with (no separeate installation is i remember
correctly)
...but bear in mind that it's a very weak database in terms of
functionality...
- no decision required about which database (mysql, postgress) to
learn
That's not true, you're choosing to learn sqlite, which isn't likely to
be useful for any real world projects.
- no problem with removal of database (in memory), but that is between
runs, not during unit testing
There's no problem deleting databases with any rbms provided your user
has the right privileges.
Main reason that i want to remove the database, is that i create
tables dynamically, from another database with table definitions. To
run multiple tests I need to clear the database in between.
I used to think that sqlite was good for testing too, it really isn't.
I've learned the error of my ways and you should too ;-)
Do some research, decide which database you want to use and develop and
test against that. Yes, SQL is supposed to be the panacea that abstracts
away from the rdbms, but that's a lie...
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.
