I would suggest working towards improve the current function-based-index
functionality:
http://h2database.com/html/features.html#computed_columns
<http://h2database.com/html/features.html?highlight=computed&search=computed#computed_columns>
so that we could do away with the need to have computed columns, so that
we could do something like:
CREATE TABLE ADDRESS(
ID INT PRIMARY KEY,
NAME VARCHAR
);
CREATE INDEX IDX_U_NAME ON ADDRESS(UPPER(NAME));
The code you'd need to modify would live in the following classes and
methods:
org.h2.command.Parser
org.h2.command.ddl.CreateIndex
org.h2.table.RegularTable#addIndex
org.h2.index.PageBtreeIndex
org.h2.index.PageDelegateIndex (optional, only needed if the PK has
to be a functional index)
From there, you should be able to map your geometry indexes onto our
regular indexes using Hilbert curves
(http://en.wikipedia.org/wiki/Hilbert_R-tree)
and implement your geometry primitives on top of that.
On 2013-06-13 14:55, bocher wrote:
Do you have a plan to support "function based indexes" ? I known you
are very busy but we are ready to help you and propose a patch to H2.
So if you haven't any plan maybe you can give some ways to do that
(suggestions or best approach...).
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database?hl=en-US.
For more options, visit https://groups.google.com/groups/opt_out.
