Doctrine 2 - ORM
  1. Doctrine 2 - ORM
  2. DDC-2164

Extend the cache support to eAccelerator

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 2.4, 3.0
    • Fix Version/s: None
    • Component/s: ORM
    • Security Level: All
    • Labels:

      Description

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

        Activity

        Hide
        Enea Bette added a comment - - edited

        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

        Show
        Enea Bette added a comment - - edited 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
        Hide
        Marco Pivetta added a comment -

        Enea Bette 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.

        Show
        Marco Pivetta added a comment - Enea Bette 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.

          People

          • Assignee:
            Benjamin Eberlei
            Reporter:
            Enea Bette
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated: