Jason Moiron

I have done a test of this library, [reusee/mmh3](https://github.com/reusee/mmh3), a modified reusee/mmh3 to use unsafe tricks, and the [python mmh3](https://github.com/hajimes/mmh3). I've only done 128bit as that's all I'm interested in....

I haven't planned on it. It should be trivial to do with `dbm.TableFor(User{}).TableName` and some simple sql. I think I'd have to wait and see for the patch, because this...

Nice contribution. I'd like to add some testing and perhaps get vgo integration going before I leave some verisons of Go behind.

This should work after #718 / v1.3.2, please reopen if you are still having issues.

It looks like I'm going to have to create a `github.com/jmoiron/sqlx/reflect` package so that the behavior of modl and sqlx can be kept in sync wrt handling more sophisticated object...

Please do, I'll almost certainly have time to look it over at Gophercon.

This would definitely be a breaking change, because sqlx.DB exposes the *sql.DB that you pass it, since it gets embedded. It's possible to add an extra interface to the `sqlx.DB`...

`sql.DB` implements a pretty huge interface. I could see some advantages to being able to do this: ```go type LoggingDB struct { *sql.DB } func (l *LoggingDB) Query(q string, args...

Hrm, I originally had a bunch to pull in from a previous blog I wrote; I'll make sure that it'l work with 0 posts.

This is something I really want to do, and in general, I think the global things that sqlx exposed early on have all been frustrating limitations. However, I'm reluctant to...