Updated README related to migrations
@@ -157,7 +157,8 @@ Advanced usage
One way to speed this up is to change the SALESFORCE_DB_ALIAS to point to
another DB connection (preferably SQLite) during testing using the
- ``TEST_*`` settings variables. Django unit tests without SalesforceModel
+ ``TEST_*`` settings variables. Such simple tests can run without any network
+ access. Django unit tests without SalesforceModel
are fast everytimes. Special read only fields that are updated only by SFDC
e.g. ``last_modified_date`` need more parameters to be possible to save them
into an alternate database, e.g. by ``auto_now=True`` or to play with
@@ -203,8 +204,10 @@ Advanced usage
Also namespace prefixes of managed packages (prefixed with "PackageName\__"
can be automatically applied to custom fields without db_column.
-- **Meta class options** - If an inner ``Meta`` class is used, it must be a
- descendant of ``SalesforceModel.Meta`` or must have ``managed=False``.
+- **Meta class options** - If a ``Meta`` class is used, remember that the
+ default ``SalesforceModel.Meta``value ``managed=False`` will be changed to
+ True by Django if managed=False is not repeated. (probably without any
+ important consequence for you)
- **Query deleted objects** - Deleted objects that are in trash bin are
not selected by a normal queryset, but if a special method ``query_all``
@@ -215,14 +218,13 @@ Advanced usage
deleted_list = list(Lead.objects.filter(IsDeleted=True).query_all())
- **Migrations** - Migrations can be used for an alternate test database
- with SalesforceModel. Then all tables must have Meta ``managed = True`` and
- attributes db_table and db_column are required. (Migrations in SFDC
- will be probably never supported, though it was experimantally tested
- creation of a new simple table in sandbox if a development patch is
- applied and permissions increased. If anything would be implemented after
- all, a new attribute will be added to SalesforceModel for safe forward
- compatibility. Consequently, the setting ``managed = True`` can be considered
- safe as it is related only to the alternate non SFDC database configured
+ with SalesforceModel. Then all tables must have a Meta with ``managed = True``
+ or without ``managed`` attribute and attributes ``db_table`` and ``db_column``
+ are required. (Migrations in SFDC are not supported. If anything would
+ be implemented after all, only explicitly clearly selected fields and models
+ could be migrated in explicitly labeled SFDC databases.
+ Consequently, the setting ``managed = True`` can be considered
+ safe as it is related only to an alternate non SFDC database configured
by ``SF_ALIAS``.)
Foreign Key Support
