Ning Sun
Ning Sun
That sounds reasonable. It has been a while since last time I'm running into this issue. Let me check my feature branch again to refresh my context about this.
Sorry for late response. I may still have issue with current `NamedField` vector. My use-case is to implement `Structable` for `serde_json::Value` and its internal `Map`. Because the map has dynamic...
Another suggestion is to make `name` of `StructDef::Dynamic` an `Option` because the json object is typically anonymous in term of a type.
The only concern with `Mappable` is it doesn't seem to have O(1) access to value with given key name.
hi @SSebo , at least in modern postgresql clients, prepare keyword is no longer used. I have implemented prepared statement for postgresql in #925. Now it should work for most...
The situation is quite similar in postgresql, pg has parameter type inference as well, but some clients like jdbc are not using this feature at all. However, other clients like...
I would suggest to cache `LogicalPlan` as prepared statement eventually because it's the most structured form of a query. Datafusion's `LogicalPlan` is capable with parameter type inference and replacement. At...
@v0y4g3r just to clarify, is this designed to disable mysql server in `datanode`, or to remove mysql protocol support in standalone mode?
Sounds good, thanks!
Let me update this issue's title