Added a porsas db-entry to the TechEmpower web server benchmarks. Interesting to see how much the row serialization perf shows on the e2e http-api tests. and are good to see if the db configs were any good.

For next.jdbc, I've realized that :gen-fn is a terrible name for the row/result set builder option(!) so I'm going to rename it before I move to a Beta release. It'll be a breaking change for any code that is already passing a non-default builder, but I would expect that to be a very small subset of users at this point. Feedback welcome (I'll most likely change it to :builder-fn but I'd appreciate discussion/suggestions).

@ikitommi Hopefully my changes on master will solve your cache optimization issue in next.jdbc?

reducible! is also a terrible name, while we're at it

reducible <Action> <----what's the action? I have a hard time with this one

Suggestions for better names are welcome 🙂 Naming is hard.

They do say that the two hardest problems in programming are naming things, cache invalidation, and off by one errors

https://cljdoc.org/d/seancorfield/next.jdbc/ 1.0.0-alpha11 -- :gen-fn -> :builder.fn (BREAKING); documents datafy, nav, :schema stuff; adds a hook for custom builders to access the SQL string (for @ikitommi).

Also https://github.com/seancorfield/next-jdbc/issues/16 -- feedback welcome!