For actual or intended Test::Database use cases that you know about, which of
these situations are represented:
1. The test requires the actual DBMS used in production, it is designed with
only a single specific DBMS in mind, no substitutions allowed.
2. Like #1 except substitutions are allowed if the substitute is compatible for
all the DBMS syntax/capabilities used.
3. The test will work with a variety of DBMS and works to least common
denominator.
4. The test will work with a variety of DBMS and will do different things
depending on which DBMS is in use as it recognizes their different syntax or
capabilities.
5. Some other option?
Thanks in advance for the info.
-- Darren Duncan
