there's no excuse for putting sf and terra in the middle of everthing anymore, it's gone way too long - simply do not do vect() or st_read() on "/vsicurl/ http...path.to.parquet" - this avoids all the good tech and both read in full (BY DEFAULT, this amazes me so much, I actually forget ...)

Please, use {sedonadb} or {gdalraster},even {vapour} ,{lazysf} - all of these put avaliable tech *first*, those ridiculously popular legacy downstream packages aren't going to get better at this ...

@mdsumner

I do not want to be the fun police in that party but we never needed to read the whole table from a db connection for a very long time.

Still most folks are using dbreadtable (and that is fine) instead of using some basic SQL to do some filter ...

@defuneste oh I know, I saw sf run backwards as fast as possible from day 0 - I did and said what I could, total disaster
@mdsumner I wanted to say that for a lot of users a very simple wrapper is worth a lot. Yeah it is also hiding a lot but I think this is very hard to build a tool that can do both (I am not smart enough to know if that is possible or not).