Jay Pipes wrote:
Roy Lyseng wrote:
Call them status codes and this may no longer be a problem...
The point being that they don't belong in a list of *error* codes...
My point is that if you generalize error and warning codes (and other
messages - completion codes) into "status" codes, then you can treat all
messages the same. It is also a good thing to have distinct codes for
all messages, regardless of type.
Can we make the process of "registering" a new error code and message
more dynamic? With Drizzle's architecture leaning towards plugins,
the plugin should have the ability to register errors with the server
without having to restart the server...
...but have do you cause them? Engine-specific errors?
Not sure what you mean here... what does "but have do you cause them?"
mean?
Please forget my comment. I did not read your text properly.
Thanks,
Roy
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
