public inbox for [email protected]
help / color / mirror / Atom feedFrom: Simon Riggs <[email protected]>
To: Troels Arvin <[email protected]>
Cc: [email protected]
Cc: [email protected]
Subject: Re: [PATCHES] SQL conformance related patch
Date: Fri, 26 Nov 2004 19:52:28 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <1101381875.3068.27.camel@localhost>
References: <1101381875.3068.27.camel@localhost>
On Thu, 2004-11-25 at 11:24, Troels Arvin wrote:
> Simon also has ideas for improvement of the conformance documentation
> page (features.sgml), but that's probably a version 8.1 thing. I think
> he'd better describe the ideas himself.
...since you mention it, I should explain:
The sections Supported Features and Unsupported Features cover both
Mandatory (Core) and Optional features in the same section. It would be
better to separate these, just as the SQL standard itself does in Annex
F - SQL Feature Taxonomy.
This seems especially important for the Unsupported Features section,
since the length of the list makes it look like 100% support is a long
way off, whereas it is only 14 features away, and many of them minor
[see Troels' low hanging fruit list on this thread]
Many of the optional features are definitely desirable and it is useful
information to retain the Unsupported optional features, but would be
best as a separate sub-section.
Troels tells me the sections are autogenerated, which makes the
re-editing slightly more difficult, so worth consultation first.
Not sure who knows how to do that...or what techniques are considered
portable...XSLT?? other than maintaining two separate lists.
--
Best Regards, Simon Riggs
view thread (9+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: [PATCHES] SQL conformance related patch
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox