It seems to me that one of the points of using a Weblocks store, rather than using the underlying storage mechanism directly, is abstraction: code shouldn't much care what the underlying mechanism is.
Imagine my surprise, then, to discover that the CLSQL version of find-persistent-objects totally ignores slot: and value:, instead pulling the entire table. Ewwww. That seems bad to me; there should be a generic API for finding objects that have a particular value in a particular slot, since such a query should make sense no matter the backend. Before I go try to fix that, I wanted to make sure that no-one seriously disagrees. -Robin -- They say: "The first AIs will be built by the military as weapons." And I'm thinking: "Does it even occur to you to try for something other than the default outcome?" -- http://shorl.com/tydruhedufogre http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
