delayed-write-p option for view slots
Jan Rychter
for discussion.
The patch implements an additional :delayed-write-p option for view
slots. If you set it to t, then the view slot writer will get called
*after* the object has been persisted. This is useful for updating
relations, where objects need to be assigned ids and stored before
relations can be updated.
This patch is likely useless to you if you never encountered the
problem. However, if you have any many-to-many relations in your data
and you want to create new objects, you will find it indispensable. You
can't create a new object using weblocks and clsql if your object has a
many-to-many relation slot without the patch.
The reason I'm not committing this is because Slava isn't convinced this
is the right way to deal with the problem, and I fully agree. In the
meantime, it solves the problem for me.
--J.
Vyacheslav Akhmechet
> This is something that I am not committing, but I thought I'd put it up
> for discussion.
>
> The patch implements an additional :delayed-write-p option for view
> slots. If you set it to t, then the view slot writer will get called
> *after* the object has been persisted. This is useful for updating
> relations, where objects need to be assigned ids and stored before
> relations can be updated.
friendly reminder) :)
- Slava