Files changed (3)
* Another option is to create a data model using Xcode's data modeler and import it using BaseTen Assistant.
- * \image latex BaseTen-object-relationships.pdf "Relationships between BaseTen's objects" width=\textwidth
+ * \image latex object-relationships.pdf "Relationships between BaseTen's objects" width=\textwidth
+ * \image latex update-change-propagation.eps "Objects being accessed by other clients are automatically faulted as part of the update process." width=\textheight
+ * \image html update-change-propagation.png "Objects being accessed by other clients are automatically faulted as part of the update process"
* PostgreSQL's xml data type handles both XML documents and content fragments. BaseTen creates NSData objects from them by default, but if the
* table also has a constraint like <em>CHECK (xml_column IS DOCUMENT)</em>, NSXMLDocuments will be created instead. The constraint mustn't
+ * In case of BaseTen-enabled tables, column contents are compared on update to determine, which columns did actually change.
+ * Thus, any custom base data types (created with <em>CREATE TYPE</em>) used in these tables need to have the equality
+ * operator <em>=</em>. Currently, the operator needs to be accessible using the default search path. In case the custom type
+ * is such that the concept of equality doesn't apply, the operator may always return <em>false</em>. In this case
* \li Altering relations' names after having them enabled will not work. To rename relations, they need
+ * \li Altering relations' columns keys will not work. Again, disabling and re-enabling is required.
* \li Altering relations' foreign keys causes BaseTen's relationship information to become out-of-date