Yes, that exists, and it has a name! H2 in-memory database. :) (or HSQLDB or Derby)
Hope this helps. Lukas 2016-07-01 13:46 GMT+02:00 Jacob G <[email protected]>: > For unit testing, I'd like to be able to use in-memory hash tables for > data rather than a database. Rather than re-implement memory-based DAO > classes for every JOOQ-based DAO class, I'd rather have JOOQ execute itself > on hash tables. Conceptually, it seems very doable since Jooq's powerful > metadata model lends itself to being rendered and executed in alternative > ways to sql. > > Has anyone thought about this, or even worked on or implemented such a > solution? > > If I were to go about it, what approach would you suggest, and are there > existing hooks I can use to redirect Jooq to a different hash table > implementation. I see that there is a hook for connections once sql is > rendered, but I'd like to hook in before that, while the query is still an > object. Is that what AbstractDelegatingQuery is for? Any other concerns? > > -- > 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. > -- 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.
