On 10/12/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > [...] > > In other persistence layers - Hibernate comes to mind - if I directly > > create the association as I have done here, I can query that > > association before persistence. > > It's not a common use-case, though, since if you are referring to > another object, you are presumably going to save them. Django asks you > to save first.
In environments where we use Hibernate, it is a common use-case - we write a lot of unit tests (we make heavy use of TDD). Hibernate does of course introduce a lot of complexity by having the concept of the session. The main concept behind TDD is that by using unit tests (tests which test one class) to drive out the expected behaviour of your code, you end up with highly cohesive, losely coupled code which good test coverage. Having to set up a test database and test data in order to create unit tests makes writing unit tests more complicated. > > If I have to create lots of fake data, > > and always hit the database it is going to add significant bloat to my > > unit testing. > > The SQLite in-memory database (a database with the name of ":memory:") > is perfect for this sort of thing. No disk access involved. I'll certainly try that - what I think I'll do is setup some test fixtures which clean out the in-memory database before and after each test. I will of course have to maintain two separate settings - one for unit tests and one for development. Anyway, if I come up with anything interesting I'll post it back. -- sam http://www.magpiebrain.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
