http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Very nice feature! I see lots of scenerio's in a code base where I didn't make use of multi criteria (as I was more experimenting with nhibernate back then) and this will make it very easy to refactor that code for optimalisation. http://ayende.com/3979/nhibernate-futures#comment20http://ayende.com/3979/nhibernate-futures#comment20Tue, 28 Apr 2009 11:17:06 GMTCali, Batch size is for updates, futures or multi query is for reads http://ayende.com/3979/nhibernate-futures#comment19http://ayende.com/3979/nhibernate-futures#comment19Tue, 28 Apr 2009 09:10:10 GMTversus setting a default batch size? http://ayende.com/3979/nhibernate-futures#comment18http://ayende.com/3979/nhibernate-futures#comment18Tue, 28 Apr 2009 08:54:59 GMTStephen, NHibernate also supply a FutureValue() method, which you _can_ use to get an int sometimes in the future. And no, you cannot use a future inside another query (but you can used a detached criteria inside another criteria) http://ayende.com/3979/nhibernate-futures#comment17http://ayende.com/3979/nhibernate-futures#comment17Mon, 27 Apr 2009 16:21:26 GMTIs it even possible to do this transparently? for example returning an int wouldn't be possible to defer, the Future instance is important as it lets you declare 'interest' in a value before actually wanting it. Ayende, is it possible to use a future in another query? like I could get a future of int, and use that as a value in another query? (I'm guessing not). http://ayende.com/3979/nhibernate-futures#comment16http://ayende.com/3979/nhibernate-futures#comment16Mon, 27 Apr 2009 16:16:42 GMTAlberto & Kork, NHibernate tries hard not to make too much magic. http://ayende.com/3979/nhibernate-futures#comment15http://ayende.com/3979/nhibernate-futures#comment15Mon, 27 Apr 2009 13:12:18 GMTA clear explanation of a great feature. Thanks Ayende. http://ayende.com/3979/nhibernate-futures#comment14http://ayende.com/3979/nhibernate-futures#comment14Mon, 27 Apr 2009 13:06:51 GMTI was going to ask the same as korkl. Is there any reason why nhibernate doesn't do it transparently (when supported)? Or, put in other words, is there any scenario you would not want to use this feature? http://ayende.com/3979/nhibernate-futures#comment13http://ayende.com/3979/nhibernate-futures#comment13Mon, 27 Apr 2009 13:06:18 GMTMutiCrietria / MultiQuery will throw if you are not supporting the feature Future is a way to utilize this feature if it is needed. http://ayende.com/3979/nhibernate-futures#comment12http://ayende.com/3979/nhibernate-futures#comment12Mon, 27 Apr 2009 13:01:19 GMTwhat i mean is that for me it's more easy and clean from an api poin of view that client code will always use multicriteria, so if later there's a change from/to a db that support "future" feature there's no need to change the code becouse the switch between future/multicriteria is made internally by nhibernate code. my question was if that was not done becouse it was too hard or impossible to introduce in current nhiebernate code or if it is so only becouse you and other nh developers prefer this api (a.k.a. it's only for nh developers taste :) ). http://ayende.com/3979/nhibernate-futures#comment11http://ayende.com/3979/nhibernate-futures#comment11Mon, 27 Apr 2009 12:57:49 GMTJunior, Not following, but probably the answer is no. Kork, Future is simpler, _much_ simpler. http://ayende.com/3979/nhibernate-futures#comment10http://ayende.com/3979/nhibernate-futures#comment10Mon, 27 Apr 2009 12:18:30 GMTthere's some problems by design to not simply use always multicriteria that internally will use "future" implementation if the currently used db allows it? http://ayende.com/3979/nhibernate-futures#comment9http://ayende.com/3979/nhibernate-futures#comment9Mon, 27 Apr 2009 11:22:13 GMTayende, was it implemented using c# expression? http://ayende.com/3979/nhibernate-futures#comment8http://ayende.com/3979/nhibernate-futures#comment8Mon, 27 Apr 2009 11:03:58 GMTStephen, Yes, that is how it basically works. About declarative, you can do it, for the very simple stuff, but it does't really work for the real world http://ayende.com/3979/nhibernate-futures#comment7http://ayende.com/3979/nhibernate-futures#comment7Mon, 27 Apr 2009 09:36:35 GMTThats cool, I guess the Future call essentially registers itself in a set associated to that session and when you first try and get the value of any of the futures, it triggers nhibernate to multiquery the lot? I always wondered if this was possible more passively, like if you had a declarative binding to the data (like xaml for example) you could infer the same deferred execution.. but my interest was purely just to see if you could, I think theres some inherant flaws with the concept. http://ayende.com/3979/nhibernate-futures#comment6http://ayende.com/3979/nhibernate-futures#comment6Mon, 27 Apr 2009 09:28:08 GMTCurrently? MS Sql Server MySQL PostGreSQL SQLite Microsoft SQL CE http://ayende.com/3979/nhibernate-futures#comment5http://ayende.com/3979/nhibernate-futures#comment5Mon, 27 Apr 2009 09:06:25 GMTWhat databases support it? http://ayende.com/3979/nhibernate-futures#comment4http://ayende.com/3979/nhibernate-futures#comment4Mon, 27 Apr 2009 08:00:11 GMTExcellent Ayende! I will be trying this out at lunch! Ninja http://ayende.com/3979/nhibernate-futures#comment3http://ayende.com/3979/nhibernate-futures#comment3Mon, 27 Apr 2009 07:52:01 GMTJason, No, not really. But Future will automatically fail over to use standard queries if the feature is not supported on the database you are using http://ayende.com/3979/nhibernate-futures#comment2http://ayende.com/3979/nhibernate-futures#comment2Mon, 27 Apr 2009 07:39:39 GMTSo other than the change of interface, is there any difference in using this than what we've been doing up to now with MultiCriteria? http://ayende.com/3979/nhibernate-futures#comment1http://ayende.com/3979/nhibernate-futures#comment1Mon, 27 Apr 2009 06:35:01 GMT