Re: [Gramps-devel] grdb import in 2.3

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

Alex,


yeah, you got it !
But I still have some strange returns ...

> If you clear environment then all grdb files can be thrown away.
> Start new grdb file. As I said before, with new grdb file
> you do not need to worry about clean environment. In recent
> 2.2 releases the environment is per-file. Starting a new file
> gets you a new environment.

If I enable transactions and use an exported 2.2.8 grdb, then there is 
no more issue with /env
But If I enable transactions and use the current 2.2.8 grdb, then I get 
/env error


Here, a resume (import 2.2.8 grdb on Family Tree):

==transactions==

* import current 2.2.8 grdb

success :)

* import 2.2.8 exported grdb

success :)

==no transactions== (example.gramps import very slow on 2.2.8)

* import current 2.2.8 grdb

37378: ERROR: DbLoader.py: line 496: Failed to import database.
Traceback (most recent call last):
   File "/home/nono/gramps-2.3/share/gramps/DbLoader.py", line 492, in 
do_import
     importer(self.dbstate.db, filename, self.uistate.pulse_progressbar)
   File "/home/nono/gramps-2.3/share/gramps/plugins/ReadGrdb.py", line 
78, in importData
     shutil.copytree(orig_env_name,new_env_name)
   File "/usr/lib/python2.4/shutil.py", line 110, in copytree
     names = os.listdir(src)
OSError: [Errno 2] Aucun fichier ou répertoire de ce type: 
'/home/nono/.gramps/env/home/nono/pastrans.grdb'

failed :(
True, there is no ".gramps/env/home/nono/pastrans.grdb". But I removed 
.gramps/env before testing. Should be created by GRAMPS 2.2.8, no ?


* import 2.2.8 exported grdb

success :)


Question: why current 2.2.8 grdb will not create a snapshot (or /env) 
and exported 2.2.8 grdb make them ?


Difference between current grdb and exported grdb (size -4% for exported 
grdb).  Data seems to be the same (XML diffs are just change time 
variables on primary objects). It is then a GRBD issue ...



Also, seems that repositories always use change="0" as change time for 
XML on 2.2 branch !!!
Should I make a bug-report or it was a fix who avoid a bug on repositories ?