Files changed (1)
- * Some tables are created in BaseTen schema to track changes in other relations. The tables and relations
- * correspond to each other based on their names. The BaseTen tables store values for the actual relations'
- * Should tables need to be renamed, first disable the table, then rename it and finally prepare it again.
+ * Some tables are created in BaseTen schema to track changes in other relations. The association is based
+ * on relation \em oids \ref baseten_enabling_ref_1 "¹". The BaseTen tables store values for the actual
+ * relations' primary keys. Thus, changing tables' primary keys after having them enabled will not work.
+ * Should this need to be done, first disable the relation, then alter the primary key and finally enable
* In addition to using BaseTen Assistant, it is possible to enable and disable tables with SQL functions.
* The functions are <em>baseten.enable</em> and <em>baseten.disable</em> and they take an \em oid as an argument.
* BaseTen Assistant, it is possible to determine a view's primary key by inserting rows into the table.
- * Relationships that involve views are stored in automatically-generated tables. These may be refreshed view
+ * Relationships and view hierarchies among other things are stored in automatically-generated tables.
+ * These should be refreshed with the SQL function <em>baseten.refresh_caches</em> after all changes to views,
+ * <li>\anchor baseten_enabling_ref_1 PostgreSQL assigns an \em oid to each relation. This does not imply that tables should be created WITH OIDS.</li>
+ * <li>\anchor database_types_ref_1 Subject to change as NSCalendarDate might become deprecated.</li>