> Greetings.

> I have more than simple code:

> $files = Doctrine_Query::create()
>        //->useResultCache(true)
>        ->from('File f')
>        ->innerJoin('f.type t')
>        ->where('f.type_id = ?', 5)
>        ->orderBy('f.id DESC')
>        ->limit(2)
>        ->execute();

> foreach($files as $file) {
>        $justForTest = $file->type->id;
> }

> Doctrine profiler tells that there is one "execute" event, which DQL
> seems like:
> SELECT ...
> FROM files f
> INNER JOIN files_types f2 ON f.type_id = f2.id
> WHERE f.type_id = ?
> ORDER BY f.id DESC
> LIMIT 2

> And that is just what I expect.

> If uncomment useResultCache(true) line and refresh page two times,
> first query with INNER JOIN disappears, which also is expected because
> of caching. But now profiler reports about two new additional queries
> like:
> SELECT ... FROM files_types f WHERE f.id = ?

> Why does this happen, and is it correct behavior when using caching?

> Doctrine 1.0.3.

> - Jon

> On Fri, Oct 31, 2008 at 7:57 AM, Eugene Janusov <esy...@gmail.com> wrote:

>> Greetings.

>> I have more than simple code:

>> $files = Doctrine_Query::create()
>>        //->useResultCache(true)
>>        ->from('File f')
>>        ->innerJoin('f.type t')
>>        ->where('f.type_id = ?', 5)
>>        ->orderBy('f.id DESC')
>>        ->limit(2)
>>        ->execute();

>> foreach($files as $file) {
>>        $justForTest = $file->type->id;
>> }

>> Doctrine profiler tells that there is one "execute" event, which DQL
>> seems like:
>> SELECT ...
>> FROM files f
>> INNER JOIN files_types f2 ON f.type_id = f2.id
>> WHERE f.type_id = ?
>> ORDER BY f.id DESC
>> LIMIT 2

>> And that is just what I expect.

>> If uncomment useResultCache(true) line and refresh page two times,
>> first query with INNER JOIN disappears, which also is expected because
>> of caching. But now profiler reports about two new additional queries
>> like:
>> SELECT ... FROM files_types f WHERE f.id = ?

>> Why does this happen, and is it correct behavior when using caching?

>> Doctrine 1.0.3.

> --
> Jonathan H. Wage
> Open Source Software Developer & Evangelist
> http://www.jwage.com
> http://www.doctrine-project.org
> http://www.symfony-project.org

> Hmm. Can't understand…

> I've found what is the problem. Doctrine_Record::serialize() removes
> references before serialization, therefore data of joined models is not
> cached at all.

> But then I've found that section "7.1.12 Serializing" of User Manual
> states: "Records can be serialized, but remember: Doctrine cleans all
> relations, before doing this." So, it looks like a "documented" behavior.

> --
> Best regards,
> Eugene Janusov.