Database Entities

Resonance's database wrapper over Swoole's connection pools does not use the Active Record pattern. Instead, it uses read-only Database Entities (which are intentionally little more than basic PHP objects), hydrated directly from a query result.

This approach allows multiple easy optimizations, like Reusing Database Queries in GraphQL, or just simple performance optimizations, like fetching just the required columns from the database.

If you need ORM features you use the Doctrine integration instead.

Using Database Entities is more performant, but Doctrine provides more ease-of-development features.


First, you have to define your data model (an instance of DatabaseEntity):

<?php namespace App\DatabaseEntity; use Distantmagic\Resonance\DatabaseEntity; final readonly class BlogPost extends DatabaseEntity { public function __construct( public string $content, public string $slug, public string $title, ) {} }

Then you need a query that hydrates the given model:

<?php namespace App\DatabaseQuery; use App\DatabaseEntity\BlogPost; use Generator; use PDO; use Distantmagic\Resonance\DatabaseQuery; /** * @template-extends DatabaseQuery<Generator<int, BlogPost>> */ final readonly class SelectBlogPosts extends DatabaseQuery { const SQL = <<<'SQL' SELECT blog_posts.content, blog_posts.slug, blog_posts.title FROM blog_posts SQL; /** * @return Generator<int, BlogPost> */ public function execute(): Generator { $stmt = $this->getConnection()->prepare(self::SQL); /** * @var list<array{ * content: string, * slug: string, * title: string, * }> */ $blogPostsData = $stmt->execute()->fetchAllAssociative(); foreach ($blogPostsData as $blogPostData) { yield new BlogPost(...$blogPostsData); } } public function isIterable(): bool { return true; } }

Now, it's possible to reuse this query in Responders, GraphQL resolvers, or pretty much anywhere in the application.

Edit on GitHub