Robert von Burg
89739717f2
This is required because in certain instances it is important to lock the object before retrieving it, otherwise if, for instance in execution, we would need to fetch, lock and re-fetch to be sure we have the latest object. In moste of the Update*Commands this is not important as we perform a list commit wins, where the client wants their version to be persisted. Later a optimistic locking can be performed in that the given version must be the latest, otherwise an exception would be thrown |
||
|---|---|---|
| .. | ||
| src | ||
| .gitignore | ||
| LICENSE | ||
| README.md | ||
| pom.xml | ||
README.md
li.strolch.service
Service API for Strolch
Running tests
Start PostgreSQL console and create the users:
$ sudo -u postgres psql
$ postgres=#
create user cacheduser with password 'test';
create database cacheduserdb;
GRANT ALL PRIVILEGES ON DATABASE cacheduserdb to cacheduser;
GRANT CONNECT ON DATABASE cacheduserdb TO cacheduser;
create user transactionaluser with password 'test';
create database transactionaluserdb;
GRANT ALL PRIVILEGES ON DATABASE transactionaluserdb to transactionaluser;
GRANT CONNECT ON DATABASE transactionaluserdb TO transactionaluser;
You can revoke the privileges with the following:
revoke ALL PRIVILEGES ON DATABASE cacheduserdb from cacheduser;
drop user cacheduser;
drop database cacheduserdb;
revoke ALL PRIVILEGES ON DATABASE transactionaluserdb from transactionaluser;
drop user transactionaluser;
drop database transactionaluserdb;