Re: JESS: Persisitent facts

1999-10-21 Thread Ernest Friedman-Hill
This is an excellent application of the JavaBean matching capability. Basically, what you'll want to do is to write a (fairly trivial) JavaBean class for each relation which reflects the columns of that relation. The Jess defclass command will then generate the deftemplates automatically from

Re: JESS: Persisitent facts

1999-10-21 Thread burke
I'm interested in this topic, too and have given it a bit of thought. I think a good (I'll leave elegance to the eye of the beholder) solution would have four parts: * a specialized version of deftemplate that specifies the database specifics, the columns of the relation, and the key fields.

Re: JESS: Persisitent facts

1999-10-21 Thread burke
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

Re: JESS: Persistent facts

1999-10-21 Thread Emmanuel Lecharny
It could be very usefull, specially if you are using a very big number of facts - that's my problem, actually (30 000 facts and more). The 'special template' stuff, (cf Burke message) could be a good approach, but that drives to something like overloading every access method of the Fact class