Re: Plans about implementing engine parameters for tables

[Paul McCullagh]

Hi Sanja,

On Jun 6, 2008, at 12:18 PM, Sanja Byelkin wrote:

> KNOWN PROBLEMS:
>
> 1. Mistyping in parameter name or value will lead only to warning.
>
> Solution: Use SQL mode with strict parameter check (As we decided it  
> will be default).
>
> 2. Accidentally equally named parameters which mean different in  
> different
> engines and be used when engine changed.

There are 2 problems here:

- Equally named parameters that have different meaning for different  
engines.
- The same parameter (for example table encryption type) have  
different names for different engines.

> Solution: recommend engine writers prefix the key with engine name  
> or some
> common name for group of engines if they want to share parameters.

I would suggest a web-based interface (on MySQL web-site or on MySQL  
Forge) where parameter names must be registered and documented. This  
would prevent duplicate names, and would enable developers to  
determine if a parameter name already exists for the feature they plan  
to implement.

Best regards,

Paul