-- This file must exist, because its highest version number is taken as Perun code version, and is compared to
-- the current DB data version from table configurations, and if they do not match, Perun will refuse to start.

-- this update is not supported on hsql since its used only as in-memory db

3.1.68
update configurations set value='3.1.68' where property='DATABASE VERSION';

3.1.67
update configurations set value='3.1.67' where property='DATABASE VERSION';

3.1.66
update configurations set value='3.1.66' where property='DATABASE VERSION';

3.1.65
update configurations set value='3.1.65' where property='DATABASE VERSION';

3.1.64
update configurations set value='3.1.64' where property='DATABASE VERSION';

3.1.63
update configurations set value='3.1.63' where property='DATABASE VERSION';

3.1.62
update configurations set value='3.1.62' where property='DATABASE VERSION';

3.1.61
update configurations set value='3.1.61' where property='DATABASE VERSION';
