On 2019-04-29 21:19, Chapman Flack wrote:
> If the reorganization happening in this thread were to make possible
> run-time-enumerable keyword lists that could be filtered for SQL92ness
> or SQL:2003ness, that might relieve an implementation headache that,
> at present, both PgJDBC and PL/Java have
On 4/29/19 2:45 PM, Peter Eisentraut wrote:
>> A policy issue, independent of this mechanism, is how many different
>> SQL spec versions we want to show in the table.
>
> We had previously established that we want to show 92 and the latest
> two. I don't propose to change that.
An annoying API r
On 2019-04-27 17:25, Tom Lane wrote:
> Would it make more sense to have just one source file per SQL standard
> version, and distinguish the keyword types by labels within the file?
The way I have written it, the lists can be compared directly with the
relevant standards by a human. Otherwise we'
Peter Eisentraut writes:
> The SQL keywords table in the documentation had until now been generated
> by me every year by some ad hoc scripting outside the source tree once
> for each major release. This patch changes it to an automated process.
Didn't test this, but +1 for the concept.
Would i
