Cache keys are not limited to word characters

Currently the cached results and queries are saved with an md5 key anyway, so this works out of the box.

The only ones that make problems are metadata cache, which stores "Entity\Article\Category$CLASSMETADATA". As the Doctrine caching layer can be used separate from the other components, it may be a good idea to still allow arbitrary keys and mapping them internally.

Don't know the reason for Zend_Cache only supporting "\w+". When using file cache for Zend, it stores the keys in the filenames instead of hashing them, so the allowed characters have to be limited in order to be able to support a wide range of backends (files, database, etc.)...

Even base64 does not work, as it has the "+" and "/" characters (and the "=" padding character).

By stripping the = (PHP's base64 implementations does not seem to need it) and escaping + and / with the _ (not in base64), it works:

http://pastie.org/927679

But this is a really dirty hack... (md5'ing does not help, as getIds() requires the cache key encoding to be bidirectional)

If the cache keys are going to be changed this needs to happen for RC1, therefore rescheduling.

I don't think this is necessary, why would you want to nest a Zend Cache adapter inside a Doctrine Cache instead of just using that cache?

When you integrate Doctrine 2 into an existing project that uses, manages and provides Zend_Cache instances? In our case, we have centralized factories that deliver the Zend_Cache instances (depending from configuration, environment, etc.), so we don't want to add additional cache configuration logic for Doctrine.

This is not a problem that we need to fix. It's a problem with Zend Framework.
We cannot do anything here. I'd mark it as "Invalid", since it's up to Zend Framework fix their limitation.

If possible I'd make the ClassMetadata hash generator as a configuration extension.
I cannot imagine anything more than this.

@Guilherme Zend Cahce restricts the keys because of the filesystem cache. It needs proper chars i guess.

@Nico: Why not use str_replace and replace the chars into words?

$key = str_replace(array('\\', '$'), array('__NS__', '__USD__'), $key);

If you use a cache other than ArrayCache for the Annotations you need to translate that chars also, they contain other stuff that is not filesystem compliant.

This is the way I do it currently. Not the most elegant way, but it seems to work...
Which other characters are used for Annotations?

$, # and :: (dollar, hash and double colon).

Closed, this won't be changed and there is a simple workaround to be applied in the wrapping driver replacing \, ::, $, #