Seems possible but I can't say much more than that. core.logic operates on
tuples, so you could extract the resultset form the DB and pass them along
to core.logic to constrain further without much difficulty.
David
On Wed, Nov 23, 2011 at 6:24 PM, Mark <markaddle...@gmail.com> wrote:
> It occurs to me I may not have fully answered your question. I'd like
> core.logic to supply a set on constraints which my code would convert into
> a SELECT statement and then return a seq of something (vectors? maps?
> facts?) that the engine would then use to reason, potentially driving
> additional queries.
>
> I'm not familiar with core.logic internals but I suspect that the
> constrains could be expressed as a vector of relation names and maps.
> Something like [Parent-Child {:parent "Mark" :child nil}]. My SQL
> implementation would translate that into SELECT name FROM Parent,
> Parent-Child WHERE Parent-Child.id=Parent.id AND Parent.name='Mark'.
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> To post to this group, send email to clojure@googlegroups.com
> Note that posts from new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
>
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
