maria-discuss team mailing list archive
Mailing list archive
Re: The future of Dynamic Columns
Note, you can use Flexvie.ws to materialize the get_column() output into another table, index that and use an inexpensive join to retrieve the data from the original table. It isn't a perfect solution, but it is a stop-gap to function based indexes.
Sent from my iPhone
> On Feb 1, 2015, at 3:23 PM, Sergei Golubchik <serg@xxxxxxxxxxx> wrote:
> Hi, Tom!
> To sum this thread up:
> * clunky syntax is unfortunate, but that's what SQL is, that'll probably
> stay that way :(
> * A function to query a type of a value for a particular dynamic column,
> COLUMN_GET_SQL() as you call it, that should be easy to do.
> I've just created an issue for that: https://mariadb.atlassian.net/browse/MDEV-7535
> feel free to add your comments there.
> * indexes for dynamic columns (even if not "as important"). This is
> already existing MDEV-6017, but it's a much larger task than COLUMN_GET_SQL.
> * Input JSON directly - an existing task too, MDEV-7524
> * And arrays were mentioned too, it's MDEV-6632
> And while I'm not promising anything, I think that MDEV-7535
> (COLUMN_GET_SQL or something similar) has a good chance of being
> implemented in 10.2.
> Mailing list: https://launchpad.net/~maria-discuss
> Post to : maria-discuss@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~maria-discuss
> More help : https://help.launchpad.net/ListHelp