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?
Yeah, it's annoying. I have conversion routines in
replication_services.cc and also the statement_transform.cc files, both
of which must translate between the serialized field type enum in the
GPB message and the internal enum...
I would support dropping the non-GPB enum, but that is impossible until
the field merge and conversion arrays go bye-bye.
-jay
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
