I'm not sure how you are goint to implement an in-memory relational-database 
that can be used woth the same db-object-using code - that sounds ineresting...
But this has a smell of having your unit-test testing the framework, more than 
your code, the same problem that exists in django.

Ideally this should be avoided...
And it can - with mock-objects that substute the db object, emulating it's 
api-calls that your code is using. It's eazier than you might think, using the 
'mock' library - check out the link I posted.
It would also be even faster than a memory-database, and much simpler.
The only downside is that anytime your query-code changes, you would have to 
update your tests...

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to