http://snippets.dzone.com/posts Thu, 21 Aug 2008 15:53:08 GMT DZone Snippets: canonical code http://snippets.dzone.com/posts/show/756 Due to international issues, there are many ways of representing a date in SQL code. I prefer to use odbc canonical. <br /> <br />dates <br /><code> <br />{d 'yyyy-mm-dd'} <br />{d '2001-12-31'} <br /></code> <br /> <br />timestamps <br /><code> <br />{ts 'yyyy-mm-dd hh:mm:ss'} <br />{ts '2001-12-31 00:00:00'} <br /></code> <br /> <br />times <br /><code> <br />{t 'hh:mm:ss'} <br /></code> <br /> <br />Don't let the ODBC in the name fool you, these work in Microsoft SQL Server, and through ODBC connections. <br />I've tested it in Query Analyzer, Stored Procedures, ADO code (both OLEDB and ODBC providers), ADO.Net code (both SQLClient and ODBC). <br /> <br /> <br />See Microsoft reference: <br />http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcjetdate_time_and_timestamp_literals.asp <br /> <br />It is a pity that there isn't some sort of SQL standard for date representation. Or maybe there is and I don't know it? Wed, 21 Sep 2005 05:04:46 GMT http://snippets.dzone.com/posts/show/756 Will_Rickards (Will Rickards)