Re: Refactor reference.md

separate web page on the calcite site, unbundled from the SQL language page. > > > > Mihai > > > > > > From: Julian Hyde > > Sent: Wednesday, January 24, 2024 1:27 PM > > To: dev@calcite.apache.org > > Subject: Re: Refactor re

Re: Refactor reference.md

Julian Hyde > Sent: Wednesday, January 24, 2024 1:27 PM > To: dev@calcite.apache.org > Subject: Re: Refactor reference.md > > "The documentation would be incrementally improved, like the code base." Or > it might incrementally decline into a shambles. Sure, this is ope

Re: Refactor reference.md

, January 24, 2024 1:27 PM To: dev@calcite.apache.org Subject: Re: Refactor reference.md "The documentation would be incrementally improved, like the code base." Or it might incrementally decline into a shambles. Sure, this is open source, and open source can sometimes create miracles, b

Re: Refactor reference.md

; attempts to clarify something, but has not been approved since early December. > > Mihai > > From: Julian Hyde > Sent: Wednesday, January 24, 2024 12:54 PM > To: dev@calcite.apache.org > Subject: Re: Refactor reference.md > > Extr

Re: Refactor reference.md

To: dev@calcite.apache.org Subject: Re: Refactor reference.md Extra documentation would be nice. But who is going to write (and maintain) this extra documentation? Even the current documentation takes a lot of work. When reviewing a PR to add a function, I have to tell people to remove

Re: Refactor reference.md

eally > there should be examples as well. > > Mihai > > From: Cancai Cai > Sent: Wednesday, January 24, 2024 7:14 AM > To: dev@calcite.apache.org > Subject: Refactor reference.md > > Hey Calcite Devs, > > I am currently working

Re: Refactor reference.md

documentation from other databases. The behavior should be described for corner cases, and ideally there should be examples as well. Mihai From: Cancai Cai Sent: Wednesday, January 24, 2024 7:14 AM To: dev@calcite.apache.org Subject: Refactor reference.md Hey Calcite Devs

Refactor reference.md

Hey Calcite Devs, I am currently working on CALCITE-6215 . During my work, I have noticed that certain functions have multiple variations with different parameter types in their respective databases. For example, in PostgreSQL, the to_char