From: Alex R. <sh...@gr...> - 2007-06-26 17:14:01
|
On Tue, 2007-06-26 at 16:46 +0200, J=C3=A9r=C3=B4me wrote: > > 1. Enable transactions > > 2. Create a new grdb with 2.2: ~/blah.grdb > > This should create a directory ~/.gramps/env/home/nono/blah.grdb/ > > Is it not so? >=20 > yes, it is. OK, I thought I was going insane :-) > But it appears when I disable transactions ... > Creating a grdb without transactions will not create /env child. But=20 > exporting to grdb without transactions will create /env child reference=20 > for the exported grdb. This is correct. When you either work with or without transactions the grdb import will work fine. You only have a problem when you: 1. disable trannsactions 2. create grdb 3. Then enable transactions 4. Then import that grdb (created without transactions) into dbmanager. But now the transactions are enabled. I can work around this case too, but this is a twisted setup :-) > testcase: >=20 > 1. disable transactions > 2. create a new grdb (test1.grdb) on GRAMPS 2.2.x > 3. import example.gramps > #comment: slow, isn't it ?# > 4. export data to grdb (test2.grdb) > 5. close gramps > 5. look at your .gramps/env child directories No bug here. No transactions -> no environment. But all along in our previous correspondence you said that you had transactions enabled. Now I realize that they were first disabled then enabled. > Relationships between transactions and environment seems to be very=20 > complexes but in this case, something is not logical ... It is very simple an logical: grdb with transactions have env dir. That's it. I think I understand the problem now. Should be fixed soon. Alex --=20 Alexander Roitman http://www.gramps-project.org |