Skip to content

The new Doctrine chapter has landed #366

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.

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 20 commits into from
Jun 5, 2011
Merged

The new Doctrine chapter has landed #366

merged 20 commits into from
Jun 5, 2011

Conversation

weaverryan
Copy link
Member

Hey guys!

This is a complete refactor of the Doctrine chapter. This is ready - except for 3 missing diagrams - which @Leannapelham and should knock out this weekend. The only known issue is that the doctrine:generate:entity command does not currently work, but I doc'ed it here as if it did (i.e. hopefully it will soon).

This is too big of a chapter for me to have gotten everything right, so comments+proofreading much appreciated.

Thanks!

Configuring the Database
~~~~~~~~~~~~~~~~~~~~~~~~

Before you really being, you'll need to configure your database connection
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo: being = begin?

@weaverryan
Copy link
Member Author

Thanks :) - all of these changes have been integrated - I'll merge as soon as the diagrams are in there.

call the ``flush()`` method, it calculates an overall changeset and executes
the most efficient query/queries possible. For example, if you're persist
100 ``Product`` objects and then call ``persist()``, Doctrine will execute
a *single*, multi-line ``INSERT`` query (assuming your database engine supports
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is wrong, it will just create a single prepared statement and re-use that. Multi line insert is not supported across all vendors.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And all databases support prepared statements (or PDO emulates that for them, but that is not something important for users to know)

with visible name, price, description properties) and a "product" table
on the right, with name, price and description columns. In the middle
is Doctrine, which is handling a two-way street, transforming data in
both directions.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The diagram is still missing.

weaverryan added a commit that referenced this pull request Jun 5, 2011
The new Doctrine chapter has landed
@weaverryan weaverryan merged commit 57650f7 into master Jun 5, 2011
@weaverryan
Copy link
Member Author

I've merged the PR so that it makes it into the next docs build. But I'm happy to address any other comments (and the diagrams were just added).

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants