fnp
/
django-cas-provider.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (from parent 1:
6eca12e
)
corrected formatting
author
Sebastian Annies
<sebastian.annies@googlemail.com>
Mon, 10 Oct 2011 18:10:49 +0000
(21:10 +0300)
committer
Sebastian Annies
<sebastian.annies@googlemail.com>
Mon, 10 Oct 2011 18:10:49 +0000
(21:10 +0300)
README.rst
patch
|
blob
|
history
diff --git
a/README.rst
b/README.rst
index
9720936
..
258d685
100644
(file)
--- 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:
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:
to circumvent that problem you will need to fake the initial migration: