On Jun 25, Zardosht Kasheff wrote:
> This is a feature request that adds grammar for "clustering" indexes.
> Users can define an index to be clustering (include all of the columns
> in the index), and as a result, a flag is passed into the handler via
> a flag. It is up to the storage engine to properly implement it.
> Storage engines that choose to not implement it can simply ignore the
> I am interested to hear feedback on this feature and patch. Here is
> the link:
I don't have anything in particular against this patch, besides the fact
that I'd rather avoid extending the grammar indefinitely for every
A generic approach would be better, something like Sanja's patch that
Monty was referring to. The goal of it was about allowing storage
engines to extend CREATE TABLE with arbitrary attributes - keyword=value
pairs - per table, per column, and per index. Not as general as
arbitrary syntax extensions in arbitrary places, but also much simpler.
The engine would only need to specify the names of the attributes and
their types (similar to my_getopt), like "PAGE_FILL_FACTOR, per table,
floating point, in the 0..1 range; CLUSTERED, boolean, per index" etc.
Regards / Mit vielen Grüßen,
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Sergei Golubchik <serg@stripped>
/ /|_/ / // /\ \/ /_/ / /__ Principal Software Engineer/Server Architect
/_/ /_/\_, /___/\___\_\___/ Sun Microsystems GmbH, HRB München 161028
<___/ Sonnenallee 1, 85551 Kirchheim-Heimstetten
Geschäftsführer: Thomas Schroeder, Wolfgang Engels, Wolf Frenkel
Vorsitzender des Aufsichtsrates: Martin Häring