History

Robert von Burg e7cf9bad6d [Fix] Fixed undo logic for general commands Should a command be undone, then some commands performed an undo, although they didn't perform their work, this led to an inconsistent data model. I.e. AddResourceCommand would fail because the resource already existed and an undo would lead to the existing object being removed		2016-11-03 13:35:29 +01:00
..
src	[Fix] Fixed undo logic for general commands	2016-11-03 13:35:29 +01:00
.gitignore	moved everything to a subdirectory for repo merge	2014-09-16 08:53:28 +02:00
LICENSE	moved everything to a subdirectory for repo merge	2014-09-16 08:53:28 +02:00
README.md	[Project] Updated project for deployment to Maven Central	2016-09-22 09:37:55 +02:00
pom.xml	[Project] Remove xmlpers as dependency from service project	2016-11-03 12:10:43 +01:00

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;