Skip to content
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

Refine Explanations of Doctrine orm Package Structure #11710

Merged
merged 2 commits into from
Nov 11, 2024
Merged
Changes from 1 commit
Commits
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
Next Next commit
Update architecture.rst
  • Loading branch information
Speelwolf authored Nov 7, 2024
commit 8c8a4e6183a3b0b0d18886c129096569eeae5ee2
11 changes: 5 additions & 6 deletions docs/en/reference/architecture.rst
Original file line number Diff line number Diff line change
Expand Up @@ -33,14 +33,13 @@ Doctrine ORM is divided into four main packages.
- ORM (depends on DBAL+Persistence+Collections)

This manual mainly covers the ORM package, sometimes touching parts
of the underlying DBAL and Persistence packages. The Doctrine code base
is split in to these packages for a few reasons and they are to...
of the underlying DBAL and Persistence packages. The Doctrine codebase
is split into these packages for a few reasons:


- ...make things more maintainable and decoupled
- ...allow you to use the code in Doctrine Persistence and Collections
without the ORM or DBAL
- ...allow you to use the DBAL without the ORM
- To make things more maintainable and decoupled
greg0ire marked this conversation as resolved.
Show resolved Hide resolved
- To allow you to use the code in Doctrine Persistence and Collections without the ORM or DBAL
- To allow you to use the DBAL without the ORM

Collection, Event Manager and Persistence
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Expand Down