Comments on: Why Future<T> should be in your future http://elegantcode.com/2009/11/16/why-futuret-should-be-in-your-future/ Tue, 16 Mar 2010 18:16:58 -0500 http://wordpress.org/?v=2.8.6 hourly 1 By: Davy Brion http://elegantcode.com/2009/11/16/why-futuret-should-be-in-your-future/comment-page-1/#comment-50457 Davy Brion Wed, 18 Nov 2009 11:46:57 +0000 http://elegantcode.com/2009/11/16/why-futuret-should-be-in-your-future/#comment-50457 <a href="#comment-50454" rel="nofollow">@RichB</a> it also works on MySQL, PostgreSQL, SQLite, and SQL Server CE @RichB

it also works on MySQL, PostgreSQL, SQLite, and SQL Server CE

]]> By: RichB http://elegantcode.com/2009/11/16/why-futuret-should-be-in-your-future/comment-page-1/#comment-50454 RichB Wed, 18 Nov 2009 10:54:59 +0000 http://elegantcode.com/2009/11/16/why-futuret-should-be-in-your-future/#comment-50454 > So why aren’t you using it? It's only supported on MSSQL. > So why aren’t you using it?

It’s only supported on MSSQL.

]]>