On Tue, Mar 6, 2012 at 2:56 AM, Ivo Roper <[email protected]> wrote: > I've been looking at the parser and dispatch code in drizzled/sql_parser and > want to do some refactoring to clean up sql_base, sql_parse and the related > sql_xxxx files. I would then write a SQL dispatcher class as recommended by > Brian. (Blueprint to come...) > > Before I dive in any deeper, does anyone have any advice or cautions > regarding the task and/or that code? I've written a blueprint to summarize > what I intend to do here: code-cleanup-misplaced-drizzled-functions
This part seems straightforward and totally makes sense. I haven't worked with this part of the code, but it is obviously desirable that all methods of the same class are found in one file. I'm more interested in the SQL dispatcher class. Does it mean I could create a plugin (say stored_procedures) that would register its own SQL syntax? (say "CALL functionname()") henrik -- [email protected] +358-40-8211286 skype: henrik.ingo irc: hingo www.openlife.cc My LinkedIn profile: http://www.linkedin.com/profile/view?id=9522559 _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp

