<Replying to ejfried>
You're right. I haven't been thinking of this in Rete terms. But,
having to assert all the rows at once is the definition of the
problem. In a large database, this is just not acceptable. And the
property change issue is non-trivial also since databases (at least
the ones I use) don't tell you when something has changed. You have to
do a query and find out, and you don't want your bean continuously
polling the database any more than you want JESS doing it.
So I'm not sure what the solution would look like:
A restriction that allows a single database-backed pattern as the last
clause in a rule's LHS? This seems like a hack to me.
A mechanism that checks the validity of database assertions "one last
time" before the rule actually fires?
A mechanism that locks a database row when a Rete node has latched
onto it? (But you don't want it locking an entire table.)
In any case, I think what the other writer and myself are interested
in would in fact require some closer interaction with the Rete engine
than the beans interface allows.
--
robin
=:-{)
University of California, Irvine
Information and Computer Science Dept.
http://www.ics.uci.edu/~burke/
"The universe is made of stories, not of atoms" - Muriel Rukeyser
---------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the
list (use your own address!) List problems? Notify [EMAIL PROTECTED]
---------------------------------------------------------------------
