Alexander Plavin

Thanks! I'm still not very familiar with this (piracy/invalidations/...) part of julia development, so may be mistaken that the current approach is optimal...

version is fine, please merge

some tests still fail on nightly

With new commits, everything should pass on both nightly and older versions.

CanonicalIndexError should be fixed with https://github.com/JuliaLang/julia/pull/47008

> I decided a better option would be to call float on all endpoint types 10^16+1 ∈ (10^16+1)..10^17 true julia> 10^16 ∈ (10^16+1)..10^17 false ``` Maybe, just promoting two endpoints...

> and wait for this https://github.com/JuliaLang/julia/pull/46453 to land. I don't think this is necessary. Just fixing StaticArrays setindex should be enough - it's just called in Accessors as is: https://github.com/JuliaObjects/Accessors.jl/blob/f0a65fe0edb542324574eaeef5680e78335415ba/src/staticarrays.jl#L3

@iamed2 well, here is a very simple reproducible example: ``` fetch!(NamedTuple, execute(conn, " select array_agg(schemaname) from pg_tables ")).array_agg[1] ``` gives a string, which in my case looks like this: ```...

That would be useful indeed. I'm not familiar with the postgres api, does it just return everything as strings and you parse them into whatever datatype?

bump