Databases
StackOverflow2013
Postsdbo
POCustom Fields in Doctrine MongoDB Document
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCustom Fields in Doctrine MongoDB Document
    primarykey
    data
    text
    <p>I have a specific requirement in a project that requires the use of <code>MongoDB Collection</code>, that contains <code>Documents</code> with different field sets.</p> <p>For example, these two <code>Documents</code> are in the same Collection. The <code>name</code> and <code>foo</code> fields are mandatory.</p> <pre><code>{ 'name': 'scott', 'foo': 'abc123' } { 'name': 'jack' , 'foo': 'def456', 'bar': 'baz' } </code></pre> <p>Using Doctrine MongoDB ODM, the <code>Document</code> fields would be specified in a <code>Document</code> class.</p> <p>As for now, I have my <code>Document</code> class extending the following <code>BaseDocument</code> and created a custom listener for <code>PostPersist</code> event, to update the persisted <code>Document</code> with the custom fields.</p> <p><code>BaseDocument</code> class:</p> <pre><code>class BaseDocument { protected $customFields; public function __construct() { $this-&gt;customFields = array(); } public function setCustomField($name, $value) { if (\property_exists($this, $name)) { throw new \InvalidArgumentException("Object property '$name' exists, can't be assigned to a custom field"); } $this-&gt;customFields[$name] = $value; } public function getCustomField($name) { if (\array_key_exists($name, $this-&gt;customFields)) { return $this-&gt;customFields[$name]; } throw new \InvalidArgumentException("Custom field '$name' does not exists"); } public function getCustomFields() { return $this-&gt;customFields; } } </code></pre> <p><code>postPersist</code> listener:</p> <pre><code>class CustomFieldListener { public function postPersist(LifecycleEventArgs $args) { $dm = $args-&gt;getDocumentManager(); $document = $args-&gt;getDocument(); $collection = $dm-&gt;getDocumentCollection(\get_class($document)); $criteria = array('_id' =&gt; new \MongoID($document-&gt;getId())); $mongoDoc = $collection-&gt;findOne($criteria); $mongoDoc = \array_merge($mongoDoc, $document-&gt;getCustomFields());; $collection-&gt;update($criteria, $mongoDoc); } } </code></pre> <p>The current solution is not elegant at all, and requires both <code>insert</code> and <code>update</code> calls to insert a single <code>Document</code>. What is the better way to inject custom fields into the <code>Document</code> when persisting, reading &amp; updating?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USdezull
    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. This table or related slice is empty.
    1. VO
      singulars
      1. POCustom Fields in Doctrine MongoDB Document
      1. USfdellutri
      1. VTFavorite
    1. COHave you considered Inheritance Mapping? http://docs.doctrine-project.org/projects/doctrine-mongodb-odm/en/latest/reference/inheritance-mapping.html
      singulars
      1. POCustom Fields in Doctrine MongoDB Document
      1. USdbrumann
    2. CO@mahok I don't see how it can be done using that. Perhaps you could provide an example?
      singulars
      1. POCustom Fields in Doctrine MongoDB Document
      1. USdezull
    3. COYou can have a BaseDocument with common properties and then have multiple documents inheriting from that class with their own properties, e.g. a BarDocument with bar-property. This way you don't have to resort to using magic like in `getCustomField()`
      singulars
      1. POCustom Fields in Doctrine MongoDB Document
      1. USdbrumann
 

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