#1329: Doctrine 2 support
-------------------------+--------------------------------------------------
Reporter: david | Owner: david
Type: enhancement | Status: new
Priority: normal | Milestone: 1.0.5
Component: database | Version:
Severity: normal | Keywords:
Has_patch: 0 |
-------------------------+--------------------------------------------------
Comment(by david):
Replying to [comment:2 saracen]:
> Just noticed the [ticket:1267 Add support for Doctrine query/result
caching.] ticket, which is related to the issues you'll have implementing
Doctrine 2 support.
>
> Pure XML configuration for these adaptors is going to be a headache. It
feels like you'd have to go to great lengths to achieve that and the only
way I see is hacky solutions.
>
> Extending the adaptors is easy enough (add class to autoload and
database configs), so I would suggest by default the adaptors just do a
sane amount of work required to be useful and then make them extremely
easy to be configured by extending them.
>
> We don't want to be copying code that already exists in initialize(), so
on the off chance we find that we can't add configuration rules after the
base initialize() method has been run, we could perhaps implement some
method hooks like $this->getCacheInstance() or $this->setupCache() etc.
Would this be possible purely via Doctrine event listeners as suggested in
comment:ticket:1267:1?
Predefined hooks definitely won't cut it; it needs to be more generic,
like {{{$this->callbackAfterConnectionSetup()}}} or whatever so people can
do crazy stuff we can't imagine right now. Otherwise, we'll always have to
catch up with whatever features the Doctrine guys add.
--
Ticket URL: <http://trac.agavi.org/ticket/1329#comment:3>
Agavi <http://www.agavi.org/>
An MVC Framework for PHP5
_______________________________________________
Agavi Tickets Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/tickets
