> Unfortunately I cannot rely on all access going through the writers
> specified in the slot definition. Unfortunately there is a great deal of
> existing code that uses (setf slot-value), with-slots, etc. in this
> codebase.
Ew. Sounds like sed or M-x replace-regexp might the most sane solution
Hello,
I definitely understand your concerns about magic here--I'd prefer the
explicit Postmodern approach for sure if I were starting from scratch.
Unfortunately I cannot rely on all access going through the writers
specified in the slot definition. Unfortunately there is a great deal of
existin
Hi Eli,
I really want to stay as far away from the kind of magic that is
giving database abstactions a bad name. So I don't really think
*db-auto-sync* is a feature that fits in Postmodern.
Doesn't looping over the slots in your class, and defining :after
methods on their setters, solve this with
Hello,
I'm in the process of converting an existing application from CLSQL to
Postmodern. This application makes heavy use of CLSQL's *db-auto-sync*
feature, whereby new instances of view (DAO) classes are immediately
inserted into the DB table, and changes to view class instance slots result
in i
