I'll note that "CREATE_DB" is slightly misleading, and would be more
accurately called "CREATE_SEPARATE_TEST_DB_IN_ORACLE".
The error I'm getting is somewhat misleading also as there's nothing wrong
with the ALWAYS keyword, the problem is that the test script is trying to
create a table in a database I thought it had been told not to create
anything in. Instead it is calling `'CREATE TABLE "DJANGO_MIGRATIONS" ("ID"
NUMBER(11) GENERATED BY DEFAULT ON NULL AS IDENTITY NOT NULL PRIMARY KEY,
"APP" NVARCHAR2(255) NULL, "NAME" NVARCHAR2(255) NULL, "APPLIED" TIMESTAMP
NOT NULL)'` and then rightly falling over because this is a READ-ONLY DB.
The ability to tell Django that a database is Read-Only would be a greatly
appreciated feature!
I'm continuing to try and work this issue through though if anyone has
solve this (or similar), please tell me how? :)
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/3305bdbd-f8cd-4ea1-b883-48c62191efc0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
