Future: support for hardening parts of a schema into a tabular representation

[mozilla]

Future: support for hardening parts of a schema into a tabular representation

[ncalexan]

An alternate approach that trades much of the convenience of your "table assertion" approach above in favour of true SQL power would be to expose an (sql ...) function to the query engine. I assumed we wanted some kind of (places-bookmarks ...) query function already; this would be similar. (Compare (fulltext ...).) Such a function would be strictly more general, allow for much fancier SQL representations, and require potentially simpler support in the query engine. Of course, it also makes it much less pleasant to transact new data against this representation ... but even that could be addressed by extending the EDN accepted by the transactor to accept, for example

[(table "visits"
  :page/visitTime ...
  :page/visitDevice ...
  :page/visitType ...)]

such an approach could even write to Places if needed.