Hi Deven,
I see you've been busy :) I'm trying to respond to all your mails in one.
There's definitely room for improving the documentation around the
> MockDataProvider... There are MANY cases where I would like to use the bind
> values to help determine the result sets and that is not documented
> anywhere other than playing with the API. I will try to write up some
> concise docs on using the bind values as well as the query matching to be
> added. Other than that, I imagine it would be ideal to just somehow pass an
> identifier somehow so that you can explicitly choose a mock result for each
> query... I'm not sure what that would look like or how it could be
> implemented; but I will think on it..
Yes, that's true. The MockDataProvider has been introduced as an
experimental API at first with little documentation. It looks like the
general direction is fine, but we haven't been working on it much any more.
I'm curious about your bind variable use-case. Could you elaborate a bit
more, perhaps?
2014-06-25 3:22 GMT+02:00 Deven Phillips <[email protected]>:
> Pull request cancelled and recreated after implementing unit tests and
> more debugging.
>
> https://github.com/jOOQ/jOOQ/pull/3349
>
I'll review that as soon as possible.
Also, looks like the TravisCI builds are all passing and so it appears
> there will be no regressions by incorporating these changes...
>
> Woot!
>
Congrats ;-)
--
You received this message because you are subscribed to the Google Groups "jOOQ
User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
