DDC-2164: Extend the cache support to eAccelerator #2723

Closed
opened 2026-01-22 14:01:43 +01:00 by admin · 3 comments
Owner

Originally created by @doctrinebot on GitHub (Nov 23, 2012).

Jira issue originally created by user noise085:

It would be nice if the Doctrine caching drivers would support the eAccelerator library.

Originally created by @doctrinebot on GitHub (Nov 23, 2012). Jira issue originally created by user noise085: It would be nice if the Doctrine caching drivers would support the eAccelerator library.
admin added the ImprovementWon't Fix labels 2026-01-22 14:01:43 +01:00
admin closed this issue 2026-01-22 14:01:43 +01:00
Author
Owner

@doctrinebot commented on GitHub (Nov 23, 2012):

Comment created by @ocramius:

[~noise085] eAccelerator is known for being stripping comments from cached source (making it impossible to use annotations)... Do you happen to know if this is fixed? Supporting it as cache driver is fine btw, I just wonder how many users will start thinking of using eAccelerator and then will be facing this huge limitation.

@doctrinebot commented on GitHub (Nov 23, 2012): Comment created by @ocramius: [~noise085] eAccelerator is known for being stripping comments from cached source (making it impossible to use annotations)... Do you happen to know if this is fixed? Supporting it as cache driver is fine btw, I just wonder how many users will start thinking of using eAccelerator and then will be facing this huge limitation.
Author
Owner

@doctrinebot commented on GitHub (Nov 26, 2012):

Comment created by noise085:

I know that eAccelerator has this issue. It would be nice if we could utilize it with XML, YML and PHP based mapping though.
Do you know if the same problem would appear with these kinds of mapping strategies?

To give response to your question (eAccelerator and annotations incompatibility), there is a pull request on github, https://github.com/eaccelerator/eaccelerator/issues/19 .

It seems that in the future these could be resolved, and at that time it would be very nice to have that supported with doctrine (symfony2 already has support for this library).

"I just wonder how many users will start thinking of using eAccelerator and then will be facing this huge limitation". Sometimes users just does not have a choice. Imagine the case when you have a hosted site that requires caching functionalities and the only available cache library is eAccelerator (as just in my case). You would be fried as a chicken hehe :)

@doctrinebot commented on GitHub (Nov 26, 2012): Comment created by noise085: I know that eAccelerator has this issue. It would be nice if we could utilize it with XML, YML and PHP based mapping though. Do you know if the same problem would appear with these kinds of mapping strategies? To give response to your question (eAccelerator and annotations incompatibility), there is a pull request on github, https://github.com/eaccelerator/eaccelerator/issues/19 . It seems that in the future these could be resolved, and at that time it would be very nice to have that supported with doctrine (symfony2 already has support for this library). "I just wonder how many users will start thinking of using eAccelerator and then will be facing this huge limitation". Sometimes users just does not have a choice. Imagine the case when you have a hosted site that requires caching functionalities and the only available cache library is eAccelerator (as just in my case). You would be fried as a chicken hehe :)
Author
Owner

@Majkl578 commented on GitHub (Sep 11, 2017):

eAccelerator no longer exists for recent PHP versions.

@Majkl578 commented on GitHub (Sep 11, 2017): eAccelerator no longer exists for recent PHP versions.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#2723