Databases
StackOverflow2013
Postsdbo
PORestore document with embedded documents on ODM
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORestore document with embedded documents on ODM
    primarykey
    data
    text
    <p>Here are two sample classes I have:</p> <pre><code>/** @ODM\Document */ class Product implements JsonSerializable{ /** @ODM\String */ protected $some_property; /** @ODM\EmbedMany */ protected $attributes; public function jsonSerialize(){ $o = new StdClass(); $o-&gt;property = $this-&gt;some_property; $o-&gt;attributes = $this-&gt;attributes; return $o; } } /** @ODM\EmbeddedDocument */ class Attribute implements JsonSerializable{ /** @ODM\String */ protected $some_property; public function jsonSerialize(){ $o = new StdClass(); $o-&gt;property = $this-&gt;some_property; return $o; } } </code></pre> <p>In my code, I create an instance of Product, and then some processes create an array of Attribute instances on <code>$product-&gt;attributes</code>. I persist the Product instance without a problem into mongoDB using Doctrine ODM. I can go into the DB (using rockmongo), and I see the presisted document, and the annotations on the JSON view to the class of the <code>attributes</code> array:</p> <pre><code>"_doctrine_class_name": "\Attribute" </code></pre> <p>But when I query for that product using the QueryBuilder, instead of getting an array of Attribute instances, I get a PersistentCollection (looking at the isntance with the debugger at runtime).</p> <p>I believe this has to do with <em>lazy loading</em>, but its breaking up my code. When I try to call <code>json_encode($product)</code>, instead of cascading through to each of the <code>Attribtue</code> instances, it just returns an empty array.</p> <p>Here is what I expect to get form a json_encode():</p> <pre><code>{ "property": "some product value", "attributes": [ { "property": "some attribute value" }, { "property": "some attribute value" } ] } </code></pre> <p>Is there any way to either disable <em>lazy loading</em>, or force the proper instantiation of each Attribute instance? Or any other way to be able to get the desired JSON object, without having to manually traversing the whole structure? Thanks!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USMartín Peverelli
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COWhat about not using Doctrine ODM but just raw php Mongo ?
      singulars
      1. PORestore document with embedded documents on ODM
      1. USLFI
    2. COWell... not much of a solution to the problem, since to be homogeneous I'd need to restructure the project. But what do you mean by raw php Mongo, and where can I read some tutorials or doc for that (specific in ZF2)?
      singulars
      1. PORestore document with embedded documents on ODM
      1. USMartín Peverelli
    3. COI agree, it's not a solution. But IMO you are trying to use the ODM features for working with an kind of dynamic array. If I am right, this is straightforward with [\MongoClient](http://www.php.net/manual/en/class.mongoclient.php) or [\MongoCollection](http://www.php.net/manual/en/class.mongocollection.php) as you are working directly with an array. And you can access it through doctrine-odm like this `$documentManager->getConnection()->getMongo()`. Not sure that help.
      singulars
      1. PORestore document with embedded documents on ODM
      1. USLFI
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload