Doctrine 2 - ORM
  1. Doctrine 2 - ORM
  2. DDC-1909

Getting Fatal error Call to undefined method Doctrine\ORM\Mapping\ClassMetadata::getSqlExecutor()

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.2
    • Fix Version/s: 2.2.3
    • Component/s: ORM
    • Security Level: All
    • Labels:
      None
    • Environment:

      Description

      ( ! ) Fatal error: Call to undefined method Doctrine\ORM\Mapping\ClassMetadata::getSqlExecutor() in /home/www/scms/library/Doctrine/ORM/Query.php on line 241
      Call Stack
      #	Time	Memory	Function	Location
      1	0.0000	327100	{main}( )	../index.php:0
      2	0.1485	4174724	Zend_Application->run( )	../index.php:47
      3	0.1485	4174724	Zend_Application_Bootstrap_Bootstrap->run( )	../Application.php:366
      4	0.1486	4174796	Zend_Controller_Front->dispatch( ???, ??? )	../Bootstrap.php:97
      5	0.1545	4488224	Zend_Controller_Router_Rewrite->route( object(Zend_Controller_Request_Http)[333] )	../Front.php:911
      6	0.1550	4488968	SCMS_Controller_Router_Route->match( string(6), ??? )	../Rewrite.php:398
      7	0.1567	4570028	Doctrine\ORM\AbstractQuery->getOneOrNullResult( long )	../Route.php:72
      8	0.1567	4570192	Doctrine\ORM\AbstractQuery->execute( array(0), long )	../AbstractQuery.php:571
      9	0.1567	4570660	Doctrine\ORM\Query->_doExecute( )	../AbstractQuery.php:733
      Variables in local scope (#9)
      
      $executor =
      
      	Undefined
      
      $paramMappings =
      
      	Undefined
      
      $sqlParams =
      
      	Undefined
      
      $types =
      
      	Undefined
      
      

      error appears out of the blue, after a few refreshes it disappears, but this happens constantly.

        Activity

        Hide
        Benjamin Eberlei added a comment -

        Added a guard to avoid this problem. Its not a real fix, but i cannot come up with the a way to reproduce the problem that you have exactly.

        Show
        Benjamin Eberlei added a comment - Added a guard to avoid this problem. Its not a real fix, but i cannot come up with the a way to reproduce the problem that you have exactly.
        Hide
        Justinas added a comment -

        i'm not sure, about the clean cache, it just doesn't happen all the time so it's hard to check. If i remember correctly i flushed the cache, and the error appeared, after a few refreshes it disappeared, without flushing cache. it sorta appears and disappears from time to time.

        even if i don't set the namespace for my caches i have a local memcache, so no cache collision from other projects shouldn't occur

        Show
        Justinas added a comment - i'm not sure, about the clean cache, it just doesn't happen all the time so it's hard to check. If i remember correctly i flushed the cache, and the error appeared, after a few refreshes it disappeared, without flushing cache. it sorta appears and disappears from time to time. even if i don't set the namespace for my caches i have a local memcache, so no cache collision from other projects shouldn't occur
        Hide
        Marco Pivetta added a comment -

        Justinas, setting different caches for query, results and metadata allows you to have, as an example, 3 caches writing/reading from APC. If you set a namespace for those caches, those won't collide (everything is handled transparently).

        Anyway Benjamin Eberlei is correct when he states that this shouldn't happen here. Even if your approach isn't correct (you don't need to explicitly set any cache key here, plus you should be using namespaced caches) the issue seems to be valid...

        Does this happen also with a clean cache?

        Show
        Marco Pivetta added a comment - Justinas , setting different caches for query, results and metadata allows you to have, as an example, 3 caches writing/reading from APC. If you set a namespace for those caches, those won't collide (everything is handled transparently). Anyway Benjamin Eberlei is correct when he states that this shouldn't happen here. Even if your approach isn't correct (you don't need to explicitly set any cache key here, plus you should be using namespaced caches) the issue seems to be valid... Does this happen also with a clean cache?
        Hide
        Benjamin Eberlei added a comment -

        can you try setting different namespace for Query and Metadata cache? They seem to use the same prefix. Only the Result cache uses its own prefix.

        Show
        Benjamin Eberlei added a comment - can you try setting different namespace for Query and Metadata cache? They seem to use the same prefix. Only the Result cache uses its own prefix.
        Hide
        Justinas added a comment -

        $urls is an array of URIs array('/tv/samsung/lcd', '/tv/samsung', '/tv');
        $possible_match is the value of array ex.: '/tv/samsung/lcd'

        i'm setting the namespace in the configuration, and providing a unique id for each result cache. the documentation isn't clear
        is namespace prefixed automatically if you set your cache id or is namespace ignored if you set cache id yourself.
        so i always assumed that namespace is prefixed automatically, and that you have to set cacheId yourself for same query with different parameters, so that query searching for '/tv/samsung' would not return the same result as searching for '/tv';

        Show
        Justinas added a comment - $urls is an array of URIs array('/tv/samsung/lcd', '/tv/samsung', '/tv'); $possible_match is the value of array ex.: '/tv/samsung/lcd' i'm setting the namespace in the configuration, and providing a unique id for each result cache. the documentation isn't clear is namespace prefixed automatically if you set your cache id or is namespace ignored if you set cache id yourself. so i always assumed that namespace is prefixed automatically, and that you have to set cacheId yourself for same query with different parameters, so that query searching for '/tv/samsung' would not return the same result as searching for '/tv';

          People

          • Assignee:
            Benjamin Eberlei
            Reporter:
            Justinas
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: