From 36f224f3c3165adcfb0eb862938ea37d3ad1c0d9 Mon Sep 17 00:00:00 2001 From: Sebastian Annies Date: Mon, 10 Oct 2011 21:10:49 +0300 Subject: [PATCH 1/1] corrected formatting --- README.rst | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/README.rst b/README.rst index 9720936..258d685 100644 --- a/README.rst +++ b/README.rst @@ -25,12 +25,17 @@ UPDATING FROM PREVIOUS VERSION I introduced south for DB schema migration. The schema from any previous version without south is 0001_initial. You will get an error: - Running migrations for cas_provider: - - Migrating forwards to 0001_initial. - > cas_provider:0001_initial - Traceback (most recent call last): - ... - django.db.utils.DatabaseError: relation "cas_provider_serviceticket" already exists + ``Running migrations for cas_provider:`` + + ``- Migrating forwards to 0001_initial.`` + + ``> cas_provider:0001_initial`` + + ``Traceback (most recent call last):`` + + ``...`` + + ``django.db.utils.DatabaseError: relation "cas_provider_serviceticket" already exists`` to circumvent that problem you will need to fake the initial migration: -- 2.20.1