* Perrin Harkins ([EMAIL PROTECTED]) [011017 13:27]: > Although I don't have much practical experience with it yet, this is > what I like about SPOPS: it knows its limits! I get very frustrated > with O/R mapping systems that try to handle EVERY possible data > model and come up with an enormous and inflexible API. With SPOPS, > if you have a really strange class that can't be simply mapped to > database tables you just bypass the automatic loading and write the > load method yourself. You still get a consistent API and the > security stuff. (Correct me if I've got this wrong, Chris.)
Pretty much. The security stuff is so minor to call that it's probably easier to just call it from the original program. (Note to self: put this in the manual...) Also, many of the things that make O/R tools difficult is trying to accommodate many of the actions you'll do with the objects, or do to the objects. Instead, SPOPS enables you to create rules that can be applied to objects at various trigger points. So, for instance, you can create a rule to fetch all related objects after you fetch the object itself. For version control, you can write a rule that, after a successful save, takes the old data and saves it off somewhere. The cool thing is that the rule doesn't have to care what type of object it's working on. Chris -- Chris Winters ([EMAIL PROTECTED]) Building enterprise-capable snack solutions since 1988.
