Kay,
I've also wondered about the merit of using a bytecode format for statements instead of a parse tree, but that's even further down the line.
This could be made safe with reasonable effort, should be much easier than validating a parse tree.
I really like the byte code idea. On top of multiple different parsers, prepared statements, parser plugins and query rewriting, we could use it to implement more powerful languages for stored routines. And all of that with no change necessary to the server itself!
On the other hand there is that if there is a bytecode level that we can access, someone *will* write a Drizzle BASIC or something of the sort :P
Daniel -- Daniel Fischer, MySQL Team Lead Build +46 18174400 ext. 4537 Sun Microsystems GmbH Sonnenallee 1, DE-85551 Kirchheim-Heimstetten Geschaeftsfuehrer: Thomas Schroeder, Wolfang Engels, Dr. Roland Boemer Vorsitz d. Aufs.rat.: Martin Haering HRB MUC 161028 49.011, 8.376 _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
