#!/bin/bash -e

function migration_status {
    ./manage.py migrate --list | sed 's/*/ /' > "$1"
}

template_grep_error_code=$(echo "SELECT 1 from pg_database WHERE datname='humbug_test_template';" | python manage.py dbshell --settings=zproject.test_settings | grep -q "1 row"; echo $?)

if [ $template_grep_error_code == "0" ]; then
    migration_status zerver/fixtures/available-migrations
    if [ -e zerver/fixtures/migration-status ] &&
        cmp -s zerver/fixtures/available-migrations zerver/fixtures/migration-status &&
        [ "$1" != "--force" ]; then
            psql -h localhost postgres humbug_test << EOF
DROP DATABASE humbug_test;
CREATE DATABASE humbug_test TEMPLATE humbug_test_template;
EOF
        exit 0
    fi
fi

mkdir -p zerver/fixtures

# Remove time.pyc to try to prevent it from screwing people importing
# time from inside zerver.lib.  We can drop this hack after a bit.
rm -f zerver/lib/time.pyc


echo "DROP SCHEMA humbug CASCADE; CREATE SCHEMA humbug;" | python manage.py dbshell --settings=zproject.test_settings
python manage.py syncdb --noinput --settings=zproject.test_settings
python manage.py migrate --settings=zproject.test_settings --all
migration_status "zerver/fixtures/migration-status"

# This next line can be simplified to "-n0" once we fix our app with 0 messages.
python manage.py populate_db --settings=zproject.test_settings --test-suite -n2 \
    --threads=1 --huddles=0 --personals=0 --percent-huddles=0 --percent-personals=0
python manage.py dumpdata  --settings=zproject.test_settings \
    zerver.UserProfile zerver.Stream zerver.Recipient \
    zerver.Subscription zerver.Message zerver.Huddle zerver.Realm \
    zerver.UserMessage zerver.Client \
    zerver.DefaultStream > zerver/fixtures/messages.json

# create pristine template database, for fast fixture restoration after tests are run.
psql -h localhost postgres humbug_test << EOF
DROP DATABASE humbug_test_template;
CREATE DATABASE humbug_test_template TEMPLATE humbug_test;
EOF