Hi!
On Oct 7, 2009, at 3:53 PM, Stewart Smith wrote:
we can also easily do this for any field, not just DATE.
We currently even do this for TIMESTAMP DEFAULT NOW(), it puts the
"NOW()" function in the table proto (and then string compares it to
pull
it out into the unireg_check crud in the server).
So just an optional string to match against a function?
What about allowing all non-aggregate functions?
perhaps also disallowing arguments that have to be further evaluated
(e.g. you can't have "FIELDA DEFAULT MD5(FIELDB)" but you could have
"FIELDA DEFAULT MD5("PANTS")") ?
See... this is why it gets tricky. I don't know that "one size fits
all" for functions.
Cheers,
-Brian
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
