Currently, RecordDB assumes that all of the necessary record info is in one table. However, this is unlikely to hold for a relational database and would force users to build a single table with all of the record data. The current query should be the default, but there should be an option to change the query if necessary. I don't think a programmatic way of creating the query will be useful, as opposed to blocking.
Currently, RecordDB assumes that all of the necessary record info is in one table. However, this is unlikely to hold for a relational database and would force users to build a single table with all of the record data. The current query should be the default, but there should be an option to change the query if necessary. I don't think a programmatic way of creating the query will be useful, as opposed to blocking.