Does anybody know how make the data returned be sensitive to the actual querying parameters involved? Every example, I've seen has conveniently excluded mocking the results for a query with a where clause. The one example that I did find completely ignores the where clause. It seems to entail that the queries that our regexes are matching against are fully qualified SQL. In my experience, this is not the case. There are '?' placeholders for anything in the query that is literal. It seems to be completely oblivious to the fact that these parts of the query are bound when $sth->execute is called.

Am I doing something wrong? It seems that this is a major oversight for the module if it doesn't have the ability to do query-sensitive results and would be appalled that anyone would say that the module allows you to have "fine-grained" control over the results.

Can anyone illucidate the subject for me. Until, then I'm going to hold out, hoping that I'm completely wrong about the behavior of this module. I want to be wrong because I just blew a day getting our application at work to not crash when I use Test::MockDBI.