Hi Jay, On Tue, May 11, 2010 at 11:11 PM, Jay Pipes <[email protected]> wrote:
> /me espouses the usefulness of blueprints... > > Do we have a blueprint for this work? If not, Wei and Zimin, I'd be > happy to walk you through creating one, assigning it to yourself, and > the general process of completing one... > > Let me know, > > I've just registered one blueprint for it. https://blueprints.launchpad.net/drizzle/+spec/key-value-pass-down-to-storage-engine The current status is the path from sql statement to storage engine is ok, and one specific storage engine can reject it or ack it as Brian has suggested. In Stewart's original implementation, such abilities are given to 'create database', do we need this as well, I'm curious? Currently, table.proto is not changed. The key-value pair uses EngineOption to hold the information. Do we need some refactoring in this table.proto? e.g. merge TableOption with EngineOption so that it can be more consistent? Thanks. --ziminq
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
