Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bootstrap efficiency #14

Open
aquaticrna opened this issue Jun 3, 2016 · 1 comment
Open

Bootstrap efficiency #14

aquaticrna opened this issue Jun 3, 2016 · 1 comment

Comments

@aquaticrna
Copy link
Contributor

boot strap is currently very naive and is simply sending the whole db across, in order to avoid duplication distinct is being use to filter incoming id's that should be cleaned up a fair bit, might be worth transacting schema data separately from non schema data

@metasoarous
Copy link
Owner

The ids are being fetched right now directly from the index in such a way that extracting the eids gives us duplicates. Hence the need to process with distinct.

The reason I did this stupid thing was to get around the fact that Datomic doesn't let you run a datalog query for all eids in the database. Oy. The thing to do I think is to pull from [?e :db/ident] for schema, and maybe query for everything that doesn't have an ident as "app data". But both should be specifiable, the latter in particular. Once we have posh exporting it's queries to the server for scoping though, we'll use that to compute the bootstrap.

These default functions should be part of datsync.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants