Skip to content

Explain what happens if flush() fails #6894

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Dec 15, 2016
Merged

Explain what happens if flush() fails #6894

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f3b07bf
Explain what happens if `flush()` fails
ThomasLandauer Aug 19, 2016
460b74a
Integrated improvement by javiereguiluz
ThomasLandauer Aug 29, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions doctrine.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -555,6 +555,12 @@ Take a look at the previous example in more detail:
``Product`` objects and then subsequently call ``flush()``, Doctrine will
execute 100 ``INSERT`` queries using a single prepared statement object.

.. note::

If the ``flush()`` call fails, a ``Doctrine\ORM\ORMException`` exception
is thrown, which you can catch by wrapping the ``flush()`` method in a
``try...catch`` block.

Whether creating or updating objects, the workflow is always the same. In
the next section, you'll see how Doctrine is smart enough to automatically
issue an ``UPDATE`` query if the entity already exists in the database.
Expand Down