LOL!!! the same in less words ROTFL!!!
time-out removed from defaults...
3" and workdone ;)

On Wed, Mar 23, 2011 at 3:28 PM, Stephen Bohlen <[email protected]> wrote:

> So it sounds like the thought in this context is to say "Where NH exposes a
> setting that is otherwise given a reasonable default in the underlying
> driver, NH should do nothing and thus leave the driver's defaults intact.
> But where NH exposes a setting that isn't represented in the underlying
> driver, NH should set reasonable defaults for such settings."
>
> As I see it, this guidance would lead us to not actively change things like
> the default connection timeout but would leave us free to set reasonable
> defaults for things like the ADO.NET batch size in the interests of making
> it easier for NH adopters to 'get started' with a reasonable-performing
> deployment of their NH-dependent applications.
>
> Sounds reasonable to me.
>
> Steve Bohlen
> [email protected]
> http://blog.unhandled-exceptions.com
> http://twitter.com/sbohlen
>
>
> On Wed, Mar 23, 2011 at 2:19 PM, Michael Teper <[email protected]> wrote:
>
>> Right, the default for SQL Server is 30 seconds. Overriding that
>> silently, in my opinion, is counter-productive because it would not
>> necessarily be apparent to an NH user why their queries are timing out
>> at 10 seconds instead of the expected 30 and where that should be
>> changed. To me, its perfectly valid to have a control point in NH to
>> override the SQL Server default, but NH shouldn't "own" it in the
>> sense that it should be silently setting a different default.
>>
>> -Michael
>>
>> On Mar 23, 11:03 am, Richard Brown <[email protected]> wrote:
>> > All fine by me.
>> >
>> > I think the default command timeout (if not specified) is 30 seconds -
>> but
>> > 10 is an equally suitable arbitrary default.  It's easy to change
>> anyway.
>> >
>> > Sent from my Android phone.
>> >
>> > On 23 Mar 2011 17:55, "Fabio Maulo" <[email protected]> wrote:
>> >
>> > aaaaaahh ok.
>> > It could be set to others too as any other default-setting.
>> > We already use default-settings to set the driver and some others
>> properties
>> > in others dialects and, only as information, we already have, since long
>> > time, two unused variable in the base Dialect:
>> >  /// <summary></summary>
>> > protected const string DefaultBatchSize = "15";
>> >
>> > /// <summary></summary>
>> > protected const string NoBatch = "0";
>> > ;)
>> >
>> > On Wed, Mar 23, 2011 at 2:45 PM, Roger Kratz <[email protected]>
>> > wrote:
>> >
>> > > None I assumed ...
>> >
>> > --
>> > Fabio Maulo
>>
>
>


-- 
Fabio Maulo

Reply via email to