Re: [Gramps-devel] db.cursor and no database

[jerome <rom...@ya...>]

Nick, Doug,


Attached a possible temp workaround, at least for DB repair tools.

OK, it is not designed for that: where are steps on ProgressMeter,
 quick workaround, etc ...

On the other hand, we should not quit gramps during
these processes.


regards,
Jérôme

--------------------------------------------
En date de : Sam 30.5.15, Doug Blank <dou...@gm...> a écrit :

 Objet: Re: [Gramps-devel] db.cursor and no database
 À: "jerome" <rom...@ya...>
 Cc: "Gramps Development List" <gra...@li...>, "Nick Hall" <ni...@gr...>
 Date: Samedi 30 mai 2015, 15h48
 
 On Sat, May 30, 2015 at
 9:33 AM, jerome <rom...@ya...>
 wrote:
 Nick,
 
 
 
 Yes, maybe we can have two types?
 
 
 
 If there is no database
 
     and
 
       close gramps when (while) an action is still
 running.
 
 Jérôme,
 
 Let's save this
 issue for Gramps 5.0. I have some ideas on making the
 default read-only BSDDB object a bit better. I don't
 think we want to address this long-standing issue on the eve
 of the Gramps 4.2 string freeze, and going into bug fix
 mode.
 -Doug 
 
 
 eg,
 
  self.__connect_secondary()
 
   File "gramps/gen/db/write.py", line 1003, in
 __connect_secondary
 
     db.DB_DUP | db.DB_DUPSORT)
 
   File "gramps/gen/db/write.py", line 414, in
 __open_db
 
     dbmap.open(fname, table_name, dbtype, DBFLAGS_O,
 DBMODE)
 
 bsddb3.db.DBInvalidArgError: (22, 'Argument invalide --
 BDB0633 DB_AUTO_COMMIT may not be specified in
 non-transactional environment')
 
 
 
 During handling of the above exception, another exception
 occurred:
 
 
 
 Traceback (most recent call last):
 
   File "gramps/gui/plug/tool.py", line 252, in
 gui_tool
 
     callback = callback)
 
   File "gramps/plugins/tool/rebuild.py", line 81,
 in __init__
 
     self.db.rebuild_secondary(self.update)
 
   File "gramps/gen/db/write.py", line 402, in
 try_
 
     raise DbError(msg)
 
 gramps.gen.errors.DbError: <unprintable DbError
 object>
 
 
 
 What could be then the 'standard' message on bug
 reports?
 
 
 
 True, both problems are very easy to reproduce, but we
 will
 
 not only link next bug reports to #2092? Should we?
 
 
 
 I thought that a Gtk spinner in relation with progress
 bar
 
 might "force" user to wait, but that's
 something else.
 
 
 
 About the gui (gramplet loaded) with no database,
 
 maybe a minor design issue, but a fix
 
 is possible, isn't it?
 
 
 
 
 
 regards,
 
 Jérôme
 
 
 
 
 
 --------------------------------------------
 
 En date de : Ven 29.5.15, Nick Hall <ni...@gr...>
 a écrit :
 
 
 
  Objet: Re: [Gramps-devel] db.cursor and no database
 
  À: gra...@li...
 
  Date: Vendredi 29 mai 2015, 20h50
 
 
 
  Jérôme,
 
 
 
  This is a known problem.  The
 
  bug report is a duplicate of:
 
 
 
  2092: Problems when no database is open
 
  https://gramps-project.org/bugs/view.php?id=2092
 
 
 
  It is very easy to reproduce
 
  errors of this type when no family tree is
 
  open.
 
 
 
  Nick.
 
 
 
 
 
  On 29/05/15 18:05, jerome
 
  wrote:
 
  > Should we not add something more
 
  for avoiding traceback like:
 
  >
 
  > File
 
  "gramps/gui/editors/filtereditor.py", line 896,
 in
 
  on_add_clicked
 
  >     
 
  self.filter.get_name())
 
  >    File
 
  "gramps/gui/editors/filtereditor.py", line 573,
 in
 
  __init__
 
  >      taglist = taglist +
 
  [tag.get_name() for tag in dbstate.db.iter_tags()]
 
  >    File
 
  "gramps/gui/editors/filtereditor.py", line 573,
 in
 
  <listcomp>
 
  >      taglist =
 
  taglist + [tag.get_name() for tag in
 
  dbstate.db.iter_tags()]
 
  >    File
 
  "gramps/gen/db/read.py", line 1216, in g
 
  >      with curs_(self) as cursor:
 
  >    File
 
  "gramps/gen/db/read.py", line 532, in
 
  get_tag_cursor
 
  >      return
 
  self.get_cursor(self.tag_map, *args, **kwargs)
 
  >    File
 
  "gramps/gen/db/read.py", line 495, in
 
  get_cursor
 
  >      return
 
  DbReadCursor(table, self.txn)
 
  >    File
 
  "gramps/gen/db/read.py", line 182, in
 __init__
 
  >      self.cursor =
 
  source.db.cursor(txn)
 
  > AttributeError:
 
  'dict' object has no attribute 'db'
 
  >
 
  > To reproduce it on
 
  master:
 
  >
 
  > 1. open
 
  gramps, no family tree loaded
 
  > 2. on any
 
  sidebar with filter gramplet, call the filter editor
 
  > 3. On Filter editor, clic on [+] button
 
  for adding a filter rule
 
  >
 
  > https://gramps-project.org/bugs/view.php?id=8250#c42039
 
  >
 
  > Maybe adding a simple
 
  test for looking if the database exists
 
  >
 
  on: "gramps/gen/db/read.py", line 1216?
 
  >
 
  > if
 
  self.dbstate.db.db_is_open:
 
  >     
 
  ....
 
  >
 
  > or just no
 
  access to dbstate if the state
 
  > is not
 
  passing via a check?
 
 
 
 
 
  ------------------------------------------------------------------------------
 
  _______________________________________________
 
  Gramps-devel mailing list
 
  Gra...@li...
 
  https://lists.sourceforge.net/lists/listinfo/gramps-devel
 
 
 
 ------------------------------------------------------------------------------
 
 _______________________________________________
 
 Gramps-devel mailing list
 
 Gra...@li...
 
 https://lists.sourceforge.net/lists/listinfo/gramps-devel