Closed jgebal closed 9 years ago
Are the two connections to the same database schema?
Yes. Good point. Seems like profiler tables are dropped directly after reading from them by connection. I think it would be better to separate the cleanup from the read of profiler data. This way we can call cleanup in a separate loop after reading all the data for all connections.
Alternatively we could read once for each unique database-user pair. That would also solve the problem. It could also improve on performance - data would be read only once for each unique database-user.
What do you think?
The workaround for this issue is to have the plsql profiler tables created and accessible on the database prior to running the tests. This way ruby-plsql-spec is not dropping the tables but is simply removing the data from it.
@jgebal could you check if #22 helps?
To reproduce: place 2 connection definitions in database.yml have a test (that utilizes one of the connections) execute plsql-spec --coverage
And you get: