Hello!

Can you update to propel2 ?

Thanks :)

Heya,

What's the difference between your behavior, and the Query Cache Behavior.

William

Hey SNakano,

I am having the following issue by using your caching behaviour for propel.

Brief Introduction

The case is not easy. It looks like it is not an issue by your component (hopefully).
I am writing this lines to get some feedback and with the hope in my fingers that you could tell me an "hey, you have to do it just this way to fix it easily" ;-).
I am using propel for the whole data "dealing", output as well as manipulation.

Given that we have the following database table structure:

consumer:
id <int>

item_collection_to_consumer:
id <int>
consumer_id <int>
item_collection_id <int>

item_collection:
id <int>

item_to_item_collection
id <int>
item_collection_id <int>
item_id <int>

item:
id <int>

A "consumer" has a unique id.
By using the table "item_collection_to_consumer", we are able to reference zero up to infinity "item_collection"s to a "consumer".
A "item_collection" has a unique id.
By using the table "item_to_item_collection", we are able to reference zero up to infinity "item"s to a "item_collection".
A "item" has a unique id.
Foreign keys are set between the tables and are also configured in the propel schema.xml.

I added the caching behaviour to each of this tables.
I am using redis as caching backend.

When I change the connected "item_collection" for a "consumer", the "item_collection" cache gets purged, but not the "item" cache.

This is pretty bad. When I have to purge all the item cache each time I add/change/delete an entry in "item_collection_to_consumer", the whole caching might be useless.

Example

To illustrate it better, I will try to show it via the following example.

Example Data

First of all, I "output" the content of the tables described above.

Table consumer

Table item_collection_to_consumer

Table item_collection

Table item_to_item_collection

Table item

Scenario

Now, I will write down the steps, the expected result and the real result.
All the output is based on the assumption that we want to know the data fitting to the consumer with the id "1".

As you see, the cache and the database differs.
All I can assume is the following idea. While the cached data for table "item_collection_to_consumer" is purged, the cache data for the items is not purged. Thats a fact since I can see and read this in the redis cache.

Final Words

The big question, whole can we trigger the purging of the cache and ideally without doing anything on the application front.
Do you have an advice?
Do you experienced that kind of error already?
Do you need more information?

Kind regards,
stev