Databases
StackOverflow2013
Postsdbo
PODoctrine 2 multi-level OneToOne Cascade
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODoctrine 2 multi-level OneToOne Cascade
    primarykey
    data
    text
    <p>I have three Doctrine entities: Device, which has a OneToOne relationship with Device\Status, which in turn has a OneToOne relationship with Device\Status\Battery. </p> <p>I have {cascade="persist"} set between the related entities, and from what I've read, that should be all that is required for Doctrine to automatically persist each of the entities without having to do anything myself in the code.</p> <p>Here's what I'm having problems with:</p> <pre><code>$device = new \Entities\Device(); $device-&gt;setId(100); $status = $device-&gt;getStatus(); $status-&gt;setIpAddress('192.168.0.1'); $battery = $status-&gt;getBattery(); $battery-&gt;setInternalLevel(60); $em-&gt;persist($device); $em-&gt;flush(); </code></pre> <p>After executing this code, I get the following error:</p> <pre><code>Entity of type Device\Status\Battery has identity through a foreign entity Device\Status, however this entity has no identity itself. You have to call EntityManager#persist() on the related entity and make sure that an identifier was generated before trying to persist 'Device\Status\Battery'. In case of Post Insert ID Generation (such as MySQL Auto-Increment or PostgreSQL SERIAL) this means you have to call EntityManager#flush() between both persist operations. </code></pre> <p>My question is: what is the correct way to setup my entities to ensure that they're persisted in the correct order?</p> <p>The code for the entities can be found here: <a href="https://gist.github.com/1753524" rel="noreferrer">https://gist.github.com/1753524</a></p> <p>All tests have been performed using the Doctrine 2.2 sandbox.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USTaeram
    1. USTaeram
    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
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODoctrine 2 multi-level OneToOne Cascade
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODoctrine 2 multi-level OneToOne Cascade
      1. USTaeram
      1. VTBountyStart
    3. VO
      singulars
      1. PODoctrine 2 multi-level OneToOne Cascade
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI had almost same problem. U have to call flush between each persist.
      singulars
      1. PODoctrine 2 multi-level OneToOne Cascade
      1. USCappY
    2. CO@CappY According to the Doctrine docs, since I have {cascade="persist"} set for each entity, I don't need to manually persist each entities. This code *should* work as is. http://readthedocs.org/docs/doctrine-orm/en/latest/reference/working-with-associations.html#transitive-persistence-cascade-operations
      singulars
      1. PODoctrine 2 multi-level OneToOne Cascade
      1. USTaeram
    3. COPlease provide a [short, self contained, correct example](http://sscce.org/). Your code triggers an access violation when attempting to assign values directly to `protected` properties, ie `$device->id = 100`
      singulars
      1. PODoctrine 2 multi-level OneToOne Cascade
      1. USPhil
 

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