No it is not being worked on, there are a lot of issues in relation tothis that make it quite hard to accomplish in a sane way as when thereis an update called on a child of a record then you have to invalidateboth the parent and child's cache data to do it properly. This is nosmall task. It is on the wish-list however honestly I believe we maybe better to offer a few extra classes to handle this and let theprogrammer handle it themselves. Caching should really be applicationlevel not ORM level IMO, but that said, if there was a sane way to doit on a Propel level, i'd be QUITE interested to see it.