diff options
author | louiz’ <louiz@louiz.org> | 2017-12-27 18:53:08 +0100 |
---|---|---|
committer | louiz’ <louiz@louiz.org> | 2017-12-27 18:53:08 +0100 |
commit | e4122880b5a9208aa97807ea517f70375a824a1e (patch) | |
tree | 5cce1069821e7bf5ca23049823521f8882c03d81 | |
parent | bb2dd2b69306517c85bfe59dee323cf94ef34292 (diff) | |
download | biboumi-e4122880b5a9208aa97807ea517f70375a824a1e.tar.gz biboumi-e4122880b5a9208aa97807ea517f70375a824a1e.tar.bz2 biboumi-e4122880b5a9208aa97807ea517f70375a824a1e.tar.xz biboumi-e4122880b5a9208aa97807ea517f70375a824a1e.zip |
Add a documentation to explain how to migrate from sqlite3 to postgresl
fix #3319
-rw-r--r-- | CHANGELOG.rst | 29 | ||||
-rwxr-xr-x | scripts/dump_sqlite3.sh | 21 |
2 files changed, 50 insertions, 0 deletions
diff --git a/CHANGELOG.rst b/CHANGELOG.rst index 8744858..c619c00 100644 --- a/CHANGELOG.rst +++ b/CHANGELOG.rst @@ -11,6 +11,35 @@ Version 7.0 - Fix the iq result sent at the end of a MAM response. Some clients (e.g. gajim) would throw an error as a result. +Sqlite3 to PostgreSQL migration +------------------------------- + +If you used biboumi with the sqlite3 database backend and you want to +start using postgresql instead, follow these simple steps: + + - Make sure your Sqlite3 database has the correct format by running at + least biboumi version 6.0 against this database. Indeed: biboumi can + upgrade your database scheme by itself automatically when it starts, but + the migration process can only migrate from the latest known schema, + which is the one in version 6.x and 7.x. If you are migrating from + version 6.x or 7.x, you have nothing to do. + - Start biboumi (at least version 7.0) with db_name configured to use + your postgresql database: this will create an empty database, create all + the tables with all the rights columns, ready to be filled. + - Backup your database if you value it. The migration process will not + write anything into it, so it your data should theorically be kept + intact, but we never know. + - Run the dump script found in biboumi’s sources: + `<scripts/dump_sqlite3.sh>`_. Its first and only argument must be the path + to your sqlite3 database. For example run `./scripts/dump_sqlite3.sh + /var/lib/biboumi/biboumi.sqlite`. This will create, in your current + directory, some sqlite files that contain instructions to be fed into + postgresql. + - Import all the ouput files thusly created into your PostgreSQL, with + something like this: `psql postgresql://user@password/biboumi < *.sql`. + This takes a few minutes if your database is huge (if it contains many + archived messages). + Version 6.1 - 2017-10-04 ======================== diff --git a/scripts/dump_sqlite3.sh b/scripts/dump_sqlite3.sh new file mode 100755 index 0000000..88f3097 --- /dev/null +++ b/scripts/dump_sqlite3.sh @@ -0,0 +1,21 @@ +#!/bin/sh + +sqlite3_args=$@ + +function dump_table { + table=$1 + columns=$2 + echo ".mode insert $table +.output $table.sql +select $columns from $table;" | sqlite3 $sqlite3_args +} + +dump_table "roster" "local, remote" + +dump_table "ircserveroptions_" "id_, owner_, server_, pass_, afterconnectioncommand_, tlsports_, ports_, username_, realname_, verifycert_, trustedfingerprint_, encodingout_, encodingin_, maxhistorylength_" + +dump_table "ircchanneloptions_" "id_, owner_, server_, channel_, encodingout_, encodingin_, maxhistorylength_, persistent_, recordhistory_" + +dump_table "globaloptions_" "id_, owner_, maxhistorylength_, recordhistory_, persistent_" + +dump_table "muclogline_" "id_, uuid_, owner_, ircchanname_, ircservername_, date_, body_, nick_" |