Hey Stewart, libdrizzle will probably always contain it's own set, and I don't think this should be merged with drizzled. Inside libdrizzle, there is (or will be soon), a master TYPE enum, as well as an enum for Drizzle protocol types and MySQL protocol types (there are mapping tables between the generic and protocol specific types). Also, at some point I would like to have libdrizzle be an optional dependency. If you *only* want to use the to-be-written HTTP interface for Drizzle, there is no reason to require libdrizzle or the plugin it rode in on.
I would be in full support of only having one enum type inside of drizzled though. -Eric On Wed, Nov 04, 2009 at 05:23:35PM +1100, Stewart Smith wrote: > Having two sets of ENUMs for types just seems stupid. > > well... three really (including libdrizzle). > > Ideas for synergy? > > Maybe just what's in the proto? > -- > Stewart Smith > > _______________________________________________ > Mailing list: https://launchpad.net/~drizzle-discuss > Post to : [email protected] > Unsubscribe : https://launchpad.net/~drizzle-discuss > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
