RetailCRM-Mirror/doctrine2
1
0
Fork 0
mirror of synced 2025-02-22 23:23:14 +03:00
Code Issues Projects Releases Wiki Activity

Clarified docs on working with objects.

Browse Source
This commit is contained in:
Roman S. Borschel 2010-05-05 11:10:00 +02:00
parent 51f9fb35c6
commit 7ffdd80bb2
1 changed files with 8 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
manual/en/working-with-objects.txt
View File

@ -82,13 +82,16 @@ Example:
> You can not reply on a generated identifier to be available directly after invoking `persist`. > You can not reply on a generated identifier to be available directly after invoking `persist`.
> The inverse is also true. You can not rely on a generated identifier being not available > The inverse is also true. You can not rely on a generated identifier being not available
> after a failed flush operation. > after a failed flush operation.
The semantics of the persist operation, applied on an entity X, are as follows: The semantics of the persist operation, applied on an entity X, are as follows:
* If X is a new entity, it becomes managed. The entity X will be entered into the database at or before transaction commit or as a result of the flush operation. * If X is a new entity, it becomes managed. The entity X will be entered into the database as a result of the flush operation.
* If X is a preexisting managed entity, it is ignored by the persist operation. However, the persist operation is cascaded to entities referenced by X, if the relationships from X to these other entities are mapped with cascade=PERSIST or cascade=ALL (see "Transitive Persistence"). * If X is a preexisting managed entity, it is ignored by the persist operation. However, the persist operation is cascaded to entities referenced by X, if the relationships from X to these other entities are mapped with cascade=PERSIST or cascade=ALL (see "Transitive Persistence").
* If X is a removed entity, it becomes managed. * If X is a removed entity, it becomes managed.
* If X is a detached entity, an InvalidArgumentException will be thrown. * If X is a detached entity, the behavior is undefined.
> **CAUTION**
> Do not pass detached entities to the persist operation.
++ Removing entities ++ Removing entities
@ -112,7 +115,7 @@ The semantics of the remove operation, applied to an entity X are as follows:
* If X is a managed entity, the remove operation causes it to become removed. The remove operation is cascaded to entities referenced by X, if the relationships from X to these other entities is mapped with cascade=REMOVE or cascade=ALL (see "Transitive Persistence"). * If X is a managed entity, the remove operation causes it to become removed. The remove operation is cascaded to entities referenced by X, if the relationships from X to these other entities is mapped with cascade=REMOVE or cascade=ALL (see "Transitive Persistence").
* If X is a detached entity, an InvalidArgumentException will be thrown. * If X is a detached entity, an InvalidArgumentException will be thrown.
* If X is a removed entity, it is ignored by the remove operation. * If X is a removed entity, it is ignored by the remove operation.
* A removed entity X will be removed from the database at or before transaction commit or as a result of the flush operation. * A removed entity X will be removed from the database as a result of the flush operation.
++ Detaching entities ++ Detaching entities
@ -163,7 +166,7 @@ Example:
> **CAUTION** > **CAUTION**
> When you want to serialize/unserialize entities you have to make all entity properties > When you want to serialize/unserialize entities you have to make all entity properties
> protected, never private. The reason for this is, if you serialize a class that was a proxy > protected, never private. The reason for this is, if you serialize a class that was a proxy
> instance before the private variables won't be serialized and a PHP Notice is thrown. > instance before, the private variables won't be serialized and a PHP Notice is thrown.
The semantics of the merge operation, applied to an entity X, are as follows: The semantics of the merge operation, applied to an entity X, are as follows: