On 1/9/09, Brian Aker <[email protected]> wrote: > > Hi! > > On Jan 9, 2009, at 2:55 PM, Roy Lyseng wrote: > > Note also that the standard defines e.g CURRENT_TIME(precision), where >> precision defines the split-second precision of the value. Even though >> Drizzle does not currently support arbitrary time precision, I'd suggest you >> delete the CURRENT_TIME() syntax because it is redundant and it might be >> confused with the precision specification syntax. >> > > I am betting that 90% of the applications out there, just use now().
You're telling me Drizzle doesn't have some easy end-user aliasing mechanism? I should be able to make SHEERI() an alias to CURRENT_TIMESTAMP() if I want, and then half this discussion goes away. Granted, nobody's pulled out SYSDATE() yet (which isn't actually a synonym, but the only people who use SYSDATE() are folks who don't understand how it's different than NOW()....which is why MySQL has implemented the --sysdate-is-now option). -Sheeri http://www.pythian.com/blogs/1295/does-anybody-really-know-what-time-it-is
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
