RE: Best design for a table using variant data

2012-08-20 Thread Rick James
(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 spe

RE: Best design for a table using variant data

2012-08-12 Thread Gaston Gloesener
inal Message- From: Carsten Pedersen [mailto:cars...@bitbybit.dk] 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. I

Re: Best design for a table using variant data

2012-08-10 Thread Carsten Pedersen
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,