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.

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

Jump to bottom

Add ER-model link #1462

Merged
merged 5 commits into from
Sep 11, 2024
+11 −0
Merged

Add ER-model link #1462

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
8f49ffc
Add ER-model link
sushmangupta Aug 29, 2024
7e8af55
Update ER diagram for Shopwrae6 version
sushmangupta Aug 30, 2024
2f715ad
Update pdf format erd and adjust instructions
sushmangupta Sep 6, 2024
7b6bddb
remove sw6 erd in mermaid format
sushmangupta Sep 6, 2024
ea0cbef
Update concepts/framework/data-abstraction-layer.md
bojanrajh Sep 11, 2024
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
4 changes: 4 additions & 0 deletions concepts/framework/data-abstraction-layer.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,8 @@ nav:

In contrast to most Symfony applications, Shopware uses no ORM, but a thin abstraction layer called the data abstraction layer \(DAL\). The DAL is implemented with the specific needs of Shopware in mind and lets developers access the database via pre-defined interfaces. Some concepts used by the DAL, like Criteria, may sound familiar to you if you know [Doctrine](https://symfony.com/doc/current/doctrine.html) or other ORMs. A reference to more in-depth documentation about the DAL can be found below.

Refer to [Shopware entity relationship model](../../../docs/snippets/mermaid-diagrams/sw-6.6.5.1.mermaid) dipicts different tables with different colors and their relationship.
sushmangupta marked this conversation as resolved.
Show resolved Hide resolved

### CRUD operations

An EntityRepository is used to interact with the DAL. This is the recommended way for developers to interface with the DAL or the database in general.
Expand Down Expand Up @@ -76,3 +78,5 @@ The DAL was designed to be optimized for use in ecommerce. One principle has pro
* A product is called X times every X seconds by a customer.

This varies depending on the store, but the ratio is always the same. Data records are read way more often than they are written. Therefore it is worthwhile to spend a little more time on the writing process in order to minimize the effort required for the reading process. This is done in the DAL via the Entity Indexer pattern. As soon as a product record is written, the corresponding Product Indexer is triggered, which pre-selects certain aggregations and writes them away optimized for the later reading process.


Loading
Loading