Changes between Initial Version and Version 1 of Ticket #6148, comment 112


Ignore:
Timestamp:
04/16/12 12:50:44 (3 years ago)
Author:
akaariai
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #6148, comment 112

    initial v1  
    33  - set database specific schema by settings.py DATABASES setting 'SCHEMA'.
    44  - when running raw SQL you will need to use connection.qname to get the schema qualified table name of a model (the tests contain plenty of examples, search for qname in regressiontests/queries/tests.py).
    5   - note that on MySQL and Oracle the schemas must be prefixed by the database alias to avoid collisions between production and testing. This is the reason for the above qname usage - you do not know the table's qualified name, and it will be different in testing and production.
     5  - note that on MySQL and Oracle the schemas is automatically prefixed by the database alias to avoid collisions between production and testing. This is the reason for the above qname usage - you do not know the table's qualified name, and it will be different in testing and production.
    66  - do not test the patch on a database instance containing production data. It is possible that running tests will drop your production schemas instead of testing schemas. This should not happen, but the feature is currently alpha quality...
    77
Back to Top