(and uncompressing) the JSON.
-Original Message-
From: Gaston Gloesener [mailto:gaston.gloese...@web.de]
Sent: Sunday, August 12, 2012 10:58 PM
To: mysql@lists.mysql.com
Subject: RE: Best design for a table using variant data
You don't specify how many different types (including
]
Sent: Friday, August 10, 2012 15:33
To: Gaston Gloesener
Cc: mysql@lists.mysql.com
Subject: Re: Best design for a table using variant data
You don't specify how many different types (including min/max values) you
expect to be using. If you expect to end up with a few hundred, then you
should perhaps
Hello,
I am currently facing a design where a table (virtually) needs to store
attributes of a topic (related table). The attributes can be user defined,
i.e. not known at development type and depend on other factors. Each
attributes value can be one of different types (int, int64, double,
You don't specify how many different types (including min/max values)
you expect to be using. If you expect to end up with a few hundred, then
you should perhaps consider using an ENUM or SET column directly in the
data table.
/ Carsten
On 10.08.2012 10:51, Gaston Gloesener wrote:
Hello,
