From: Doug B. <dou...@gm...> - 2011-11-10 16:17:53
|
On Thu, Nov 10, 2011 at 11:10 AM, Paul Franklin <pf....@gm...> wrote: > On 11/10/11, Michiel Nauta <m.d...@he...> wrote: >> Hi, >> >> I see on the bug tracker that a large group of errors that all deal with >> the "DbEnviromentError" are set to resolved. If I then look at what the >> solution was, revision 18292, it consists of the removal of a LOG.error >> message. I fail to see how the removal of a log message can solve >> genuine problems with loading of the database. Can someone explain this >> to me? >> >> Michiel >> > > The specific complaint in all cases was the reported log > message, caused by the line which has now been removed. > > It was never claimed to solve ALL "problems with loading > of the database." > > Now, if people try to load an incompatible database they > will get a proper error message, one which does NOT say > or imply that there is a problem with gramps which must > be then reported. Instead they will be directed on how to > try to recover or successfully load their database, via a > more-appropriate dialog box. Also, apparently the LOG.error() call is not just a log message (as I thought too). It appears that that line just kills the processing right there, rather than just writing the error and continuing with the proper error messages. At least that is what I understand Paul to say. -Doug > > ------------------------------------------------------------------------------ > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |