Ezra Epstein

Sort of. But no need for the type explicitly, it is inferred: ``` public static R insert(String poolName, String sql, Object[] params) { try { return new QueryRunner(getDataSource(poolName)).insert(sql, new ScalarHandler(),...

Presumably of I created the class that's being inserted I'd also know what type to expect for the ID. And if I ain't sure I can also introspect the type....

Well, one way is to: a) allow the logic as-is for Create - just assign the tenantId as is being done; b) check the tenantId for Update and Delete operations...

would be helpful to be able to view the example app

In particular, are you planning to include an SDK for coinbase commerce in this package? In the meantime, I've opened and share: https://github.com/tokenopoly/coinbase-commerce-core-jpa [coinbase-commerce-core-jpa](https://github.com/tokenopoly/coinbase-commerce-core-jpa) a github repo

Idempotence as a design goal in this case seems a bit unexpected. While graph traversal IS based on a set of non-modifying operations, the idea of some sequences of steps...

this looks like a (potential) security hole