On Jun 6, 2008, at 4:10 PM, Sanja Byelkin wrote:
> On Fri, Jun 06, 2008 at 03:32:43PM +0200, Sergei Golubchik wrote:
>> Hi!
>>
>> On Jun 06, Sanja Byelkin wrote:
>>> It is about "MySQL plugin interface: syntax extensions for CREATE
>>> TABLE" and for them who writes thier own engines.
>>>
>>> If you have some ideas or you see something wrong please say ASAP.
>>>
>>> Syntax will looks like this:
>>> CREATE TABLE table(
>>> id INT ENGINE_OPTIONS(OPT1=123, OPT2='someval',OPT3=aflag),
>>> INDEX USING BTREE (id)
>>> ) ENGINE = MEMORY
>>> ENGINE_OPTIONS(loc1='/mnt/d1/bigdat/mine',loc2=/mnt/d2/bigdata/
>>> mine') ;
>>
>> Uh, wasn't Monty saying that there should be no visible difference
>> for
>> the end user between built-in and engine options ? Just for the
>> change,
>> I agree with this completely. I expected the syntax to be
>>
>> CREATE TABLE table(
>> id INT OPT1=123 OPT2='someval' OPT3=aflag OPT4,
>> INDEX USING BTREE (id)
>> ) ENGINE=MEMORY loc1='/mnt/d1/bigdat/mine' loc2=/mnt/d2/bigdata/
>> mine';
>>
>> Regards / Mit vielen Grüssen,
>> Sergei
>
> yes, You are right, I just careless copied example from worklog,
> sorry.
Doesn't that mean the worklog is also in error? :-)
--
Paul DuBois
Sun Microsystems / MySQL Documentation Team
Madison, Wisconsin, USA
www.mysql.com
