ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to implement custom entities in Shopware 6 using the Data Abstraction Layer (DAL), including migrations, EntityDefinitions, and Criteria-based repository queries.
Add domain-specific data to Shopware 6 products without overriding core classes by defining custom fields in a migration.
Deciding between Shopware's Data Abstraction Layer (DAL) and direct SQL (DBAL) is a balance of system consistency and raw performance. Learn when to use each and how to implement them.
A decision guide for Shopware 6 developers choosing between Custom Fields (JSON metadata on existing tables) and Custom Entities (dedicated DAL definitions with relationships and indexes). Includes migration examples, performance trade-offs, and a validation checklist.
Learn when to use Shopware 6's DAL Criteria for entity retrieval and when to bypass it for raw DBAL queries to optimize performance and avoid N+1 query issues.
Learn how to query Shopware entities safely using the Data Abstraction Layer’s Criteria API, with a worked example, trade‑offs, and verification steps.
Guide on choosing between Shopware 6 Custom Fields and Entity Extensions for product data. Learn when to use JSON-based attributes versus relational database extensions.
Context Shopware 6 stores all date-time values in UTC and relies on the Data Abstraction Layer (DAL) to convert timestamps to the configured system timezone during entity retrieval. This conversion is applied transparently when using repository methods or the storefront API. Problem Custom reporting queries that bypass the DAL and read directly from tables s
php