[email protected] writes: > In the model part, I have a class employee. An instance is the > result of a query form person, company, address, department, etc. tables. > > The employee would be shown in a gridtable/data/form. > Now some data changes, which means the widget change/update > the slots of the employee instance. > And then for each updated instance persist-object is called, > as a hint to update the tables of the e.g. sql database tables, > which may result in a series of insert/delete/updates of the some tables. > > So the store-api is more an interface between the gui and the model > data, or do I bark up the wrong tree?
The store API is used in two ways: * Saving CLOS instances. This is an interface between CLOS and some mysterious thing. * Querying for CLOS instances. This is used more directly by dataseq for finding lists of instances sorted and paginated in particular ways. But it still goes entirely through CLOS. -- I write stuff at http://failex.blogspot.com/ now. But the post formatter and themes are terrible for sharing code, the primary content, so it might go away sooner or later. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
