[gentoo-commits] data/gentoo-news:master commit in: 2018-01-14-gnucash/

["Aaron Swenson" <titanofold@gentoo.org>]

commit:     ed16527710bcde367ba3a4c7604c5aa6b2650034
Author:     Aaron W. Swenson <aaron <AT> grandmasfridge <DOT> org>
AuthorDate: Mon Jan 15 02:58:38 2018 +0000
Commit:     Aaron Swenson <titanofold <AT> gentoo <DOT> org>
CommitDate: Mon Jan 15 03:03:46 2018 +0000
URL:        https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=ed165277

Add 2018-01-14-gnucash

Regards GnuCash’s breaking changes in data schemas.

 2018-01-14-gnucash/2018-01-14-gnucash.en.txt | 31 ++++++++++++++++++++++++++++
 1 file changed, 31 insertions(+)

diff --git a/2018-01-14-gnucash/2018-01-14-gnucash.en.txt b/2018-01-14-gnucash/2018-01-14-gnucash.en.txt
new file mode 100644
index 0000000..334c1c0
--- /dev/null
+++ b/2018-01-14-gnucash/2018-01-14-gnucash.en.txt
@@ -0,0 +1,31 @@
+Title: GnuCash 2.7+ Breaking Change
+Author: Aaron W. Swenson <titanofold@gentoo.org>
+Posted: 2018-01-14
+Revision: 1
+News-Item-Format: 2.0
+Display-If-Installed: <app-office/gnucash-4
+
+Along with changes to use modern libraries, GnuCash 2.7+ has changed the
+schema [1] it uses for both databases and files. GnuCash will
+automatically modify the file or database in place upon open.
+
+Therefore, it is imperative that you back up any files or databases
+before using GnuCash 2.7 in case you run into an issue and want or need
+to revert back to 2.6.
+
+Close any open session of GnuCash including remote sessions, then
+follow the relevant backup instructions as follows:
+
+For XML (plain files):
+$ cp /path/to/file.gnucash /path/to/file.gnucash.bak
+
+For MySQL:
+$ mysqldump gnucash_db | xz > gnucash-2.6.sql.xz
+
+For PostgreSQL:
+$ pg_dump -U gnucash_user -Z 5 gnucash_db > gnucash-2.6.sql.gz
+
+For SQLite:
+$ cp /path/to/sqlite.file.gnucash /path/to/sqlite.file.gnucash.bak
+
+[1] https://github.com/Gnucash/gnucash/releases/tag/2.7.0a