On 2014-04-03, 7:22 AM, Tim Bunce wrote:
I'd caution against making a hard distinction between file and non-file DBDs
as it may influence the design it ways that cause limitations later.
It seems to me that the key distinction is "can we reliably and safely
create and delete a private database". That's true for file-based DBDs
(ie create a subdirectory and rm -rf it afterwards) but may also be true
for some non-file DBDs in some situations.
I agree with this. There is also precedent.
As I recall the DBD::Pg test suite will create a whole new Postgres database
cluster and associated server process in order to do its testing, these are
completely separate files in their own directory and separate server on its own
port, so isolated from any production/other use of Postgres that may be on the
system.
Such solutions should be utilized by a generic database testing infrastructure
where ever possible. In such cases there is no distinction between "file based"
and not.
-- Darren Duncan
