B4J Question Change place of key_value_temp.dat

[schimanski]

Related to this,

KeyValueStore class - Simple and efficient key/value data store

where does B4J save the data in the key_value_temp.dat and is it possible to change the place, where the file is saved?

We use more server-entities parallel under linux and it seems, that every server-app needs access to the /temp/key_value_temp.dat. I don't know what happens, if more than one server writes to this file at the same time...

 

[Erel]

Why are you using an old version? Use the latest version: https://www.b4x.com/android/forum/threads/b4x-keyvaluestore-2-simple-powerful-local-datastore.63633/

 

[schimanski]

Thanks, Erel for your answer!

In most cases, i use kvs2, but related to this thread:

https://www.b4x.com/android/forum/t...ater-has-been-closed.67186/page-2#post-427303

concurrent access doesn't work with kvs2, not even if journal_mode is set to wal. Only kvs1 does it.

But now, after your reply, I remembered, that my server uses kvs2 and 1 and now i saw, that the directory of the key_value_temp.dat is inizialize in the kvs-class and could be changed....

I'm an amateur....

 

[Erel]

It is simple to make it thread safe. You need to delete the global B4XSerializator object and make it a local variable in any sub that needs it.

 

[schimanski]

You need to delete the global B4XSerializator object and make it a local variable in any sub that needs it.

The global declaration of the B4XSerializator is the reason for the inflater-exception in this discussion?

https://www.b4x.com/android/forum/t...nterexception-inflater-has-been-closed.67186/

 

[Erel]

Yes.