[Opendnssec-develop] enforcer database changes
Rickard Bondesson
rickard.bondesson at iis.se
Wed Aug 12 11:24:03 UTC 2009
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
> In getting the first part of the key backup done I have added
> a new column to a table in the enforcer database.
>
> If you need to migrate an existing database then there are
> some scripts (even though the change is trivial) in "enforcer/utils".
>
> So, for a sqlite DB run something like:
>
> sqlite3 <PATH_TO_ENFORCER.DB> < migrate_090812_1.sqlite3
>
> (This will become more important when I commit the rest of the work on
> backups.)
>
> Would folk be happier with a ksmutil command to run these
> migration scripts? (Assuming that there will be more in the future.)
>
> Sion
>
> p.s. If you are running the full setup command then this
> migration is not needed.
Will the user get a warning if it is using the new libksm on an old database?
Are you using a database scheme version number? So the user will know in what order it should apply future migration scripts.
-----BEGIN PGP SIGNATURE-----
Version: 9.8.3 (Build 4028)
Charset: utf-8
wsBVAwUBSoKmU+CjgaNTdVjaAQjVKgf/eqYmj6ESh7/Rk0LieY8+3hG6f9lSJAV4
F5+RiBEsVnsto/XtuZUqbDTaG3e8/1OyVOXyNNnc38v/lUha1ww+dXzaH68gfE2O
blYMqpLS5SKcOaFbZv1Snxbu0VnBDZC/rP+8K9TgFAOiVcOdrmSfHZyQDuj87nqg
6dgvicMVEbyuzkmTeLSg7GUrY2K3RGg9EM4nFEXb7hNFBEbv6Vlg05sRO3nJ3j+h
BPjkLfdHIe38IWmQ0aAZXdeW1udTtZtFRY7d48BEGJ7yW+4AfPEGsbfg7vtWrpjB
zqBEmGT6R0ZARrocNhyB/jvxaWtoDZjjdyra5aGjvFBJ6lq0R54PtA==
=S02d
-----END PGP SIGNATURE-----
More information about the Opendnssec-develop
mailing list