Fork me on GitHub
#datascript
<
2020-03-05
>
magra10:03:15

Have you considered namespacing the keys.

:twitter.person/id vs. :my-ns.person/id

magra10:03:06

Wilker Lucio has talked about something that might be related in his pathom talks.

magra10:03:33

He talks about having/joining data sources.

lilactown15:03:38

@magra I don’t understand what you’re saying about namespacing. yes they are namespaced. how does that help?

lilactown15:03:25

pathom is specifically built to solve basically this problem. I’m wondering if I could also have the power of a full datalog, while being able to ascertain which keys to resolve to which data source

lilactown15:03:58

I think I see what you mean. I’m not worried about different instances of person/id

lilactown15:03:23

I’m worried about if there’s some way to write a query where a namespaced keyword would be depended on, but not show up in the query at all

magra15:03:58

I am not sure I understand what you are trying to achieve. I sounds to me like a sort of "routing" to databases. I use pathom on top of two datahike dbs, one 'normal' db and a second db with legacy-data. I am not at all suggesting pathom is for you, just that the talks might yield ideas how to tackle your goal. I am just guessing here.

lilactown16:03:22

you are correct in what I am trying to achieve. I am asking about specific behavior about datalog. This answered my question in another channel: https://clojurians.slack.com/archives/C03RZMDSH/p1583387062240800?thread_ts=1583366406.238900&amp;cid=C03RZMDSH

lilactown16:03:54

so I cannot statically analyze an arbitrary datalog query and know all of the attributes it depends on