Re: Plans about implementing engine parameters for tables

[Sanja Byelkin]

On Wed, Jun 11, 2008 at 10:50:20PM +0300, Vasil Dimov wrote:
[skip]
> Or maybe add some bitmap in the my-getopt-like struct that would
> specify the allowed SQL types for the column for which the parameter was
> specified?

IMHO there can be so many details like allowed values depend on other
values and I think 100 other cases so better allow to plugin check
everything which is not  simple, and MySQL layer pre-process information
in the way required by all plugins (which need parameters) just to avoid
code and bugs (:)) duplication (which also cover all needs of engines
with simple parameters).

We also are not going process some complex types of parameters like
arrayes, trees and other structures as far as they can be represented
and saved as strings.

Main idea is to support basic needs but without limitation for some
rare/complex cases which can be implemented by engine itself. So thank
you for spotting possible limitation (I mean information about value
source).

-- 
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /    Mr. Oleksandr Byelkin <sanja@stripped>
 / /|_/ / // /\ \/ /_/ / /__   MySQL AB, Full-Time Developer
/_/  /_/\_, /___/\___\_\___/   Lugansk, Ukraine
       <___/   www.mysql.com