> > > I currently use MyISAM, but I just tried a simple
> > > create(InnoDB)/show full columns from/ and
> > > it actually does return the JSON strings I put in.
> >
> > Try it on columns with a foreign key constraint.
>
> I did and it still works (maybe the behaviour is version
> dependent?).
> > I currently use MyISAM, but I just tried a simple
> > create(InnoDB)/show full columns from/ and
> > it actually does return the JSON strings I put in.
>
> Try it on columns with a foreign key constraint.
I did and it still works (maybe the behaviour is version
dependent?).
Here is what I di
> > > Do you have any comments about this approach?
> > > What could possibly go very bad about relying on
> > > this usage of the COMMENT?
> >
> > Yes, in different storage engines, different stuff is returned.
> >
> > For example, in InnoDB, what you get returned from
> > SHOW FULL COLUMNS is not
On 9/17/07, Martijn Tonies <[EMAIL PROTECTED]> wrote:
> > Do you have any comments about this approach?
> > What could possibly go very bad about relying on
> > this usage of the COMMENT?
>
> Yes, in different storage engines, different stuff is returned.
>
> For example, in InnoDB, what you get re
Hi,
> I'm thinking of using the "COMMENT" of columns when
> creating tables to store some metadata about the
> column, for instance: valid_range of numbers,
> validation regexp, etc.
>
> I did some tests with including this information as
> a JSON (JavaScript Object Notation) string which can
> th
Hi,
I'm thinking of using the "COMMENT" of columns when
creating tables to store some metadata about the
column, for instance: valid_range of numbers,
validation regexp, etc.
I did some tests with including this information as
a JSON (JavaScript Object Notation) string which can
then be easily de
