David N. Welton

This sounds really useful, and it's similar to a change I'd likely need to add myself, to a project. Anything ever come of this?

I don't recall, at this point.

Only thing I can see that's different is that the axslx version uses a `oneCellAnchor` whereas libxlsxwriter uses a `twoCellAnchor`.

This is something I miss from xchat, and would like to see too.

Close enough I guess, but it still might be nice to be able to view the actual JSON?

Because it's a date: ``` boss_db:execute("select current_date", []). {ok,[{column,,date,4,-1,1}],[{{2014,8,1}}]} ``` Perhaps the epgsql code should be hacked to always return a datetime...?

I found the problem: it was some javascript on my end. I'm still not sure CB is 100% correct. What happens: The request starts, but it's slow because it hits...

I thought this was nice: http://highscalability.com/blog/2020/2/24/socratic-vs-euclidean-forms-of-api-documentation.html Explaining the common usage patterns, the how's and whys is as important as just listing a zillion options, most of which may be bewildering...

I think that structure sounds pretty good though.

In the tests, there is something for 'numeric', it looks like: https://github.com/epgsql/epgsql/blob/master/test/pgsql_tests.erl#L593 Where it's expected to come out as a string. That does not make sense to me, but now...