Question about sandboxing -- Journal in other location

[Ruslan Zasukhin]

On 10/19/12 1:51 PM, "Frank Lemke" <frank at knowledgeminer.com> wrote:

Hi Frank,

> Thanks Ruslan!
> Cool, works fine.

Great :)
 
> After a short testing no problems had appeared. The journal file now goes into
> the sandbox.

> The only somewhat open issue is this of multiple documents with the same name
> but different locations. This is rather exceptional, but can happen.

Yes. We think yet add into journal storage of Database.GUID property,
We have just only add it for each database.

This at least will prevent usage of journal against wrong db.


> I tried it and it seems to work (I can open two files and work with them).

> However, there is in fact only ONE journal file for both documents. I don't
> know if this is a potential problem or if you handle this situation in the
> kernel.

No no. this is VERY danger.

Problem will happens if app crashes, and on the next db.open
journal try to recover a db.

I think you need prohibit oen of second db with the same name.
Show dialog like  

   Database with name "db1" already is opened.
   Please close it to be able open "db1" from another location.

People will get into this very rare I think.


> The example is good and valuable summary of how you think things should work.
> It doesn't build, however, on my machine since the .xib file is missing
> apparently.

I will ask Sergey check it into SVN

> Also, your installer is not codesigned so it usually does not open with
> Gatekeeper enabled...

We have not switched yet to 10.8 ...
And I guess this is where this happens.

Hmm. We use old enough simple installer maker FileStorm.
So we need learn this issue. Then.

Thank you for point!

 
> Thanks, good solution.
> Frank
> 
> 
> Am 18.10.2012 um 22:20 schrieb Ruslan Zasukhin:
> 
>> On 10/4/12 6:38 PM, "Frank Lemke" <frank at knowledgeminer.com> wrote:
>> 
>>> Ahh, ok, that's right. In KM also multiple documents (dbs) can be open at
>>> the
>>> same time. So there is some potential naming conflict risk...
>>> ... There are FileManager methods to check if a file exists already ...
>>> 
>>> Am 04.10.2012 um 13:34 schrieb Ruslan Zasukhin:
>>> 
>>>> In Valentina Studio we do not want drop all possible db journals into
>>>> single
>>>> sandbox folder, because we can easy get few dbs with same name and then
>>>> problem. For YOUR application, you will use most probably single db with
>>>> same name, so no problems here, and yes you can easy use sandbox folder.
>> 
>> Hi Frank,
>> 
>> 1) we have implement this feature.
>> Described in our BLOG now.
>>    http://www.valentina-db.com/blog/
>> 
>> 
>> 
>> 2) you can download newer V4CC build with new example
>>    http://www.valentina-db.com/download/beta/5.0b48/mac_64
>> 
>> Please let us know how it works for you.

-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]