Russ, RK> On 7/29/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: >> >> So what advantages are there to the mocking approach over just replacing >> the setting?
RK> Genuine mocking (as opposed to this proposal) has one really big RK> advantage - it's lightning fast. All the db-calls get faked using a RK> cache-like setup, so it takes pretty much no time to run any db query. RK> The cost comes in keeping the mock data source up to date. I first thought on logging sql queries with result and feed them via mock. But the cost of supporting this in test-first development seems to high for me. Having to think out everything down to sql level kills most development benefits of Django ORM for me. -- Andrey V Khavryuchenko Django NewGate - http://www.kds.com.ua/djiggit/ Development - http://www.kds.com.ua Call akhavr1975 on www.gizmoproject.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?hl=en -~----------~----~----~----~------~----~------~--~---
