Sure, you can do that. You do it by creating a persistent virtual column
on the attribute, using COLUMN_GET probably, and then creating a column
on that. In a presentation on JSON and MySQL / MariaDB I show a simple
example of this:
http://www.slideshare.net/blueskarlsson/using-json-with-mariad
-
> El sáb, 26/4/14, MARK CALLAGHAN escribió:
>
> Asunto: [Maria-discuss] virtual columns and indexes on attributes in JSON
> objects
> Para: "Maria Discuss"
> Fecha: sábado, 26 de abril, 2014 17:29
>
> Does the support for
&g
erico
El sáb, 26/4/14, MARK CALLAGHAN escribió:
Asunto: [Maria-discuss] virtual columns and indexes on attributes in JSON
objects
Para: "Maria Discuss"
Fecha: sábado, 26 de abril, 2014 17:29
Does the support for
virtual columns allow
Does the support for virtual columns allow an index to be created on an
attribute in a JSON object stored in a BLOB column?
http://falseisnotnull.wordpress.com/2014/04/25/descending-indexes-in-mariadb
https://mariadb.com/kb/en/virtual-columns/
--
Mark Callaghan
mdcal...@gmail.com
___
On Tue, Nov 9, 2010 at 7:47 PM, Justin Swanhart wrote:
> This is kind of unrelated, but it seems like a good thread to ask the
> question in.
>
> Are there any plans to make an indexed virtual column work
> automatically as an index for the table? Other databases support
> 'functional' indexing,
On Tue, 9 Nov 2010 11:00:36 +0200
Henrik Ingo wrote:
Henrik> On Tue, Nov 9, 2010 at 5:03 AM, Federico Razzoli
Henrik> wrote:
Henrik> > Hello
Henrik> >
Henrik> > I've read in the documentation that any legal SQL expression
Henrik> > SHOULD be allowed in the Virtual Columns definition.
Henrik>
He
Hi Henrik,
This is kind of unrelated, but it seems like a good thread to ask the
question in.
Are there any plans to make an indexed virtual column work
automatically as an index for the table? Other databases support
'functional' indexing, that is, you can index the contents of a
function call
On Tue, Nov 9, 2010 at 5:03 AM, Federico Razzoli wrote:
> Hello
>
> I've read in the documentation that any legal SQL expression SHOULD be allowed
> in the Virtual Columns definition.
That opening statement (on http://kb.askmonty.org/v/virtual-columns)
is misleading in many ways and I've commente
Hi, Federico!
On Nov 09, Federico Razzoli wrote:
> Hello
>
> I've read in the documentation that any legal SQL expression SHOULD be
> allowed
> in the Virtual Columns definition. I'm trying to use a (deterministic) stored
> function, but I get an error:
> ERROR 1642 (HY000): Function or expres
Hi,
I don't believe that UDF or stored functions are compatible with
virtual columns. This makes sense, since these functions could be
dropped after the table is created.
--Justin
On Mon, Nov 8, 2010 at 7:03 PM, Federico Razzoli wrote:
> Hello
>
> I've read in the documentation that any legal
Hello
I've read in the documentation that any legal SQL expression SHOULD be allowed
in the Virtual Columns definition. I'm trying to use a (deterministic) stored
function, but I get an error:
ERROR 1642 (HY000): Function or expression is not allowed for column 'vc1'
Here's my create table:
CRE
5 февр. 2010, в 10:02, Oleksandr Byelkin написал(а):
[skip]
Our syntax is
[GENERATED ALWAYS] AS ( ) [VIRTUAL |
PERSISENT]
default is persistent. Syntax changed to be more compatible with MS
SQL and Oracle
Sorry I forgot something:
[GENERATED ALWAYS] AS ( ) [VIRTUAL |
PER
Hi!
5 февр. 2010, в 04:42, Federico Razzoli написал(а):
I've read that MariaDB 5.2 will support virtual columns and I've
read the virtual columns' specifications:
http://forge.mysql.com/wiki/MySQL_virtual_columns_ref_manual
I think there is a problem in that document. In CREATE TABLE and in
I've read that MariaDB 5.2 will support virtual columns and I've read the
virtual columns' specifications:
http://forge.mysql.com/wiki/MySQL_virtual_columns_ref_manual
I think there is a problem in that document. In CREATE TABLE and in ALTER TABLE
commands you can create a virtual column. The s
14 matches
Mail list logo
