A CLOS/SQL class may also be given the KnowledgeWorks mixin class, enabling rules to refer to these objects as if there were no database present. However, their database functionality carries over transparently. For example, consider the case where a slot in the database class is designated for deferred retrieval from the database. When the rulebase queries the contents of the slot, a database query will automatically be generated to retrieve and fill in the value of the slot, and the rulebase will continue as if the value had been there in the first place.
Details of the LispWorks Common SQL interface can be found in the LispWorks User Guide and Reference Manual .
(sql:def-view-class vehicle
(standard-db-object standard-kb-object)
((vehicle_no :db-kind :key)
(keeper)
(owner :db-kind :join
:db-info (:home-key :keeper
:foreign-key person_id
:retrieval :deferred
:join-class person))))
defines a database class vehicle where the person object in the keeper slot is retrieved from the person table in the database using the value of the keeper slot as key, only when queried. In the list of superclasses, standard-kb-object should appear after sql:standard-db-object.
The following example is a complete segment of code which allocates person objects to vehicle objects. Note how once the class definitions have been made, the rules do not in any way reflect the fact that there is an underlying database. The example output assumes a database initialized by the following SQL statements:
drop table VEHICLE ;
create table VEHICLE
(PLATE CHAR(8) NOT NULL, MAKE CHAR(20),
PRICE INTEGER, OWNER CHAR(20) );
grant all on VEHICLE to public ;
insert into VEHICLE values
('E265 FOO', 'VAUXHALL', 5000, '');
insert into VEHICLE values
('XDG 792S', 'ROLLS', 50000, '');
insert into VEHICLE values
('F360 OOL', 'FORD', 4000, 'PERSEPHONE');
insert into VEHICLE values
('H151 EEE', 'JAGUAR', 15000, '');
insert into VEHICLE values
('G722 HAD', 'SKODA', 500, '');
drop table PERSON ;
create table PERSON
(NAME CHAR(20) NOT NULL, SALARY INTEGER, VEHICLE CHAR(8),
EMPLOYER CHAR(20) ) ;
insert into PERSON values ('FRED', 10000, '', 'IBM');
insert into PERSON values ('HARRY', 20000, '', 'FORD');
insert into PERSON values ('PHOEBE', 5000, '', '' );
insert into PERSON values ('TOM', 50000, '', 'ACME' );
insert into PERSON values
('PERSEPHONE', 15000, 'F360 OOL', 'ICL');
drop table COMPANY ;
create table COMPANY
(NAME CHAR (20), PRODUCT CHAR(10) );
insert into COMPANY values ('IBM', 'COMPUTERS');
insert into COMPANY values ('FORD', 'CARS');
insert into COMPANY values ('ICL', 'COMPUTERS');
insert into COMPANY values ('ACME', 'TEAPOTS');
Below is an example rulebase that analyzes the database and outputs a suggestion as to which vehicle should be allocated to which person. The full code and the SQL statements to set up the database are included in the examples distributed with KnowledgeWorks.
(in-package "KW-USER")
;;; the vehicle class maps onto the car table in the
;;; database owner is a join slot which looks up the
;;; owner person object
(sql:def-view-class vehicle
(sql:standard-db-object standard-kb-object)
((number-plate :accessor vehicle-number-plate
:type (string 8)
:db-kind :key
:column plate)
(make :accessor vehicle-make
:type (string 20)
:db-kind :base
:column make)
(price :accessor vehicle-price
:type integer
:db-kind :base
:column price)
(owner-name :type (string 20)
:db-kind :base
:column owner)
(owner :accessor vehicle-owner
:db-kind :join
:db-info (:home-key owner-name
:foreign-key name
:join-class person
:set nil
:retrieval :deferred))))
;;; the person class maps onto the person table in the
;;; database
;;; vehicle is a join slot which looks up the owned
;;; vehicle object
;;; company is a join slot which looks up the company
;;; object
(sql:def-view-class person
(sql:standard-db-object standard-kb-object)
((name :accessor person-name
:type (string 20)
:db-kind :key
:column name)
(salary :accessor person-salary
:type integer
:db-kind :base
:column salary)
(vehicle-number-plate :type (string 8)
:db-kind :base
:column vehicle)
(vehicle :accessor person-vehicle
:db-kind :join
:db-info (:home-key vehicle-number-plate
:foreign-key number-plate
:join-class vehicle
:set nil
:retrieval :deferred))
(employer :type (string 20)
:db-kind :base
:column employer)
(company :accessor person-company
:db-kind :join
:db-info (:home-key employer
:foreign-key name
:join-class company
:set nil
:retrieval :deferred))))
;;; the company class maps onto the company table in
;;; the database
(sql:def-view-class company
(sql:standard-db-object standard-kb-object)
((name :accessor company-name
:type (string 20)
:db-kind :key
:column name)
(product :accessor company-product
:type (string 10)
:db-kind :base
:column product)))
;;; here we assume we have a database connected with
;;; the correct data in it - if we do we retrieve all
;;; the person and vehicle objects but company objects
;;; will be retrieved only when needed by querying
;;; the company slot of the person objects
(if sql:*default-database*
(progn (sql:select 'vehicle)
(sql:select 'person))
(format t
"~%Please connect to a database with
contents ~ created by file data.sql"))
;;; to store which vehicles a person can drive
(def-kb-struct vehicles-for-person person vehicles)
(defcontext database-example :strategy (priority))
;;; for every person initialize the list of vehicles they
;;; can drive
(defrule init-vehicles-for-person :forward
:context database-example
(person ?person vehicle nil)
-->
(assert (vehicles-for-person ? person ?person vehicles nil)))
;;; for every vehicle a person can drive which has not yet
;;; been included in the list, add it to the list
(defrule vehicle-for-person :forward
:context database-example
(person ?person vehicle nil)
(vehicle ?vehicle owner nil)
(vehicles-for-person ?c-f-p
person ?person
vehicles ?vehicles)
(test (not (member ?vehicle ?vehicles)))
; has it been included?
-->
(vehicle-ok-for-person ?vehicle ?person)
; check if ok to drive vehicle
(assert (vehicles-for-person ?c-f-p vehicles
(?vehicle . ?vehicles))))
;;; rules expressing what vehicles a person can drive:
;;; if they have no employer they can only drive a
;;; Skoda otherwise they will refuse to drive a Skoda.
;;; anyone will drive a Rolls or a Jaguar.
;;; they'll only drive a Ford or Vauxhall if salary is
;;; less than 40k.
(defrule vehicle-ok-for-person :backward
((vehicle-ok-for-person ?vehicle ?person)
<--
(person ?person company nil)
(cut)
(vehicle ?vehicle make "SKODA"))
((vehicle-ok-for-person ?vehicle ?person)
<--
(vehicle ?vehicle make "SKODA")
(cut)
(fail))
((vehicle-ok-for-person ?vehicle ?person)
<--
(or (vehicle ?vehicle make "ROLLS")
(vehicle ?vehicle make "JAGUAR"))
(cut))
((vehicle-ok-for-person ?vehicle ?person)
<--
(or (vehicle ?vehicle make "VAUXHALL")
(vehicle ?vehicle make "FORD"))
(person ?person salary ?salary)
(test (< ?salary 40000))))
;;; next to rules are just simple allocation rules,
;;; trying out each possibility until one fits
(defrule alloc-vehicles-to-persons :backward
((alloc-vehicles-to-persons ?allocs)
<--
(alloc-internal nil nil nil ?allocs)))
(defrule alloc-internal :backward
((alloc-internal ?done-persons ?done-vehicles
?allocs ?allocs)
<--
(not (and (vehicles-for-person ? person ?person)
(not (member ?person ?done-persons))))
(cut))
((alloc-internal ?done-persons ?done-vehicles
?allocs-so-far ?allocs)
<--
(vehicles-for-person ? person ?person
vehicles ?vehicles)
(not (member ?person ?done-persons))
(member ?vehicle ?vehicles)
(not (member ?vehicle ?done-vehicles))
(alloc-internal (?person . ?done-persons)
(?vehicle . ?done-vehicles)
((?person . ?vehicle) . ?allocs-so-far)
?allocs)))
;;; find a solution and print it out
(defrule find-solution :forward
:context database-example
:priority 5
(not (not (vehicles-for-person ?)))
-->
(alloc-vehicles-to-persons ?solution)
((dolist (pair ?solution)
(format t "~%~A drives ~A"
(person-name (car pair))
(vehicle-number-plate (cdr pair))))))
Below is sample output from the rulebase with SQL recording turned on to demonstrate the SQL statements that are automatically passed to the database by manipulating the objects:
KW-USER 53 > (infer :contexts '(database-example))
(SELECT VEHICLE.PLATE,VEHICLE.MAKE,VEHICLE.PRICE,VEHICLE.OWNER FROM VEHICLE
WHERE (VEHICLE.PLATE = 'F360 OOL'))
(SELECT VEHICLE.PLATE,VEHICLE.MAKE,VEHICLE.PRICE,VEHICLE.OWNER FROM VEHICLE
WHERE (VEHICLE.PLATE = ''))
(SELECT VEHICLE.PLATE,VEHICLE.MAKE,VEHICLE.PRICE,VEHICLE.OWNER FROM VEHICLE
WHERE (VEHICLE.PLATE = ''))
(SELECT
PERSON.NAME,PERSON.SALARY,PERSON.VEHICLE,PERSON.EMPLOYER
FROM PERSON WHERE (PERSON.NAME = ''))
(SELECT VEHICLE.PLATE,VEHICLE.MAKE,VEHICLE.PRICE,VEHICLE.OWNER FROM VEHICLE
WHERE (VEHICLE.PLATE = ''))
(SELECT
PERSON.NAME,PERSON.SALARY,PERSON.VEHICLE,PERSON.EMPLOYER
FROM PERSON WHERE (PERSON.NAME = ''))
(SELECT VEHICLE.PLATE,VEHICLE.MAKE,VEHICLE.PRICE,VEHICLE.OWNER FROM VEHICLE
WHERE (VEHICLE.PLATE = ''))
(SELECT
PERSON.NAME,PERSON.SALARY,PERSON.VEHICLE,PERSON.EMPLOYER
FROM PERSON WHERE (PERSON.NAME = ''))
(SELECT
PERSON.NAME,PERSON.SALARY,PERSON.VEHICLE,PERSON.EMPLOYER
FROM PERSON WHERE (PERSON.NAME = ''))
(SELECT
PERSON.NAME,PERSON.SALARY,PERSON.VEHICLE,PERSON.EMPLOYER
FROM PERSON WHERE (PERSON.NAME = 'PERSEPHONE'))
(SELECT COMPANY.NAME,COMPANY.PRODUCT FROM COMPANY
WHERE (COMPANY.NAME = 'FORD'))
(SELECT COMPANY.NAME,COMPANY.PRODUCT FROM COMPANY
WHERE (COMPANY.NAME = 'ACME'))
(SELECT COMPANY.NAME,COMPANY.PRODUCT FROM COMPANY
WHERE (COMPANY.NAME = 'IBM'))
(SELECT COMPANY.NAME,COMPANY.PRODUCT FROM COMPANY
WHERE (COMPANY.NAME = ''))
HARRY drives E265 FOO
TOM drives XDG 792S
FRED drives H151 EEE
PHOEBE drives G722 HAD
26
KnowledgeWorks and Prolog User Guide (Windows version) - 24 Mar 2017