That's exactly the kind of input I'm looking for! Functions certainly could
work for me, as long as the optimization propagates just as well as it
would with a literal (and sounds like yes, if that's the basis for
geospatial support).
On Thu, May 9, 2024 at 1:55 PM Julian Hyde wrote:
> Are you s
Are you sure that you need your constant values to be instances of
RexLiteral? A call to a 'constructor function' might do just as well.
In Calcite's geospatial support, there is no literal for the GEOMETRY
type. Expressions such as ST_PointFromText('POINT(-71.064544
42.28787)') are commonplace an
Hi all,
I'm evaluating if Calcite is a good fit as a query planner for my database
project, and would appreciate some high-level pointers on where to look in
the source to figure out how to do what I need. Or, alternatively,
confirmation if it's not feasible.
My system is relational but not SQL,
