|
|
|
|
|
|
by acveilleux
3975 days ago
|
|
|
This makes sense when you use an ORM that will transparently work. You trust the ORM to insulate you. If you have needed to go direct to SQL for something then you're looking at putting in test-specific code in your production code to simulate/fake/disable the custom SQL bit... Just run postgres on a ramdisk, or on an SSD with sync disabled and a scripted setUp/tearDown. |
|
|