[OGo-Developer] Re: Automatically Lock an Account on Failed Logins

[Adam Tauno Williams]

>I moved this thread from the users to the developer list.
>> > http://bugzilla.opengroupware.org/bugzilla/show_bug.cgi?id=1917

I think Helge already did a patch that might fix this.  Haven't tried it yet,  at a conference 
this weekend.

>After some fiddling around with gdb, I changed the return value of the 
>method canNestTransactions in sope's PostgreSQL72Context.m from NO to YES, 
>see below, then everything was working fine. The account got locked when 
>trying too many times to login with the wrong password ;)
>- (BOOL)canNestTransactions {
>  return YES;

Interesting.

>This is called from sope EOAdaptorContext.m, which is called from 
>OGoContextManager.m 
>AFAIK the nested transaction got introduced in postgres 8.0, and 7.X is 
also 
>long time not supported anymore, so I doubt that it wouldn't harm to just 
>make that little change to sope's PostgreSQL72Context.m.
>any thoughts on this?

While I agree that pg7.2 is darn old and way obsolete my experience leads 
me to believe that there are ALLOT of shops hanging on to pg72.  (Despite 
the fact that 7.2 will eventually eat your data as certainly as gravity 
turns the worlds; due to XID rollover among other issues.)  And 8.x is 
magnitudes more scalable that 7.x.