Re: Re: [VOTE] Introduce session.lock, session.lazy_write and session.lazy_destory

Hi Patrick, On Thu, Jan 30, 2014 at 2:44 PM, Patrick Schaaf <php@bof.de> wrote: > On Thursday 30 January 2014 14:34:35 Yasuo Ohgaki wrote: > > > > > Generally a really dangerous feature. minimize_lock sounds so friendly, > > > does > > > not imply danger really. > > > > > > Alternative naming proposal: unlocked_thus_unsafe > > > > It sounds good idea. How about shorter name? > > > > unsafe_lock > > Well, from the user (PHP code) level it is not a lock at all. The localized > flocking is purely for internal consistency of the individual read or write > operation, in that case. > > That's why I wanted to have 'unlocked' in the name. And for such a > dangerous > option (*) I think that a very expressive long name would be a good fit. I understand the reason. It's descriptive, but 3 words might be too long. 'transaction_lock' might be good enough for users who know DBMS, but it may not be enough for others. Does anyone have short and good name? Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net