Jay Pipes wrote:
Diego Medina wrote:
Hi,
After converting the unix_timestamp built-in function into a plugin, I
started to get a parser test failure. I looked into it and I found
that:
(looking at drizzled/error.cc )
1) When a built-in function gets the wrong number of parameters, you
get this error
"Incorrect parameter count in the call to native function ..."
2) When the same error occurs on a plugin (at least a udf plugin),
you get
"Incorrect parameters in the call to native function"
My question:
A) Do I just change the test, to expect the new error message?
B) Do I make both, the built-in functions and the udf's, use the same
error?
I would vote to make only a single error message for right now.
Would it make sense to rethink error messages, codes, and all that? It
would be really nice if:
1. Error codes were stable across releases (and forks!)
2. Error codes from the server, engines, and plugins were mutually
exclusive
3. A client program could decompose an error code to determine its
source (server, engine, or plugin)
4. Locale specific error text could be computed from error code (even
on the client)
5. A client program could decompose an error code to determine, where
possible, a generic type (i.e. file open failed, memory was
exhausted, etc.)
--
Jim Starkey
Founder, NimbusDB, Inc.
978 526-1376
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
