...
We can implement either the all tables truncate or Respawn. Whether we are going to implement one or the other is still an open question. But I think the approach we take should not be based on the performance.
Branches
I generated 2 branches just for general review. The code here is the code I moved from the initial spike (spike-postgres-tests), including the changes I made in order to accomplish the goal of the spike (
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Notice that in both cases, since it was just a spike, this is not the actual postgres implementation of the tests. Using this code as a reference, we have to work on the real implementation, where we take into account maintainability, easy to read and understand, etc.