Download the PHP package mbohuslavek/leanmapper-query without Composer
On this page you can find all versions of the php package mbohuslavek/leanmapper-query. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download mbohuslavek/leanmapper-query
More information about mbohuslavek/leanmapper-query
Files in mbohuslavek/leanmapper-query
Package leanmapper-query
Short Description Concept of Query Object for LeanMapper
License MIT
Informations about the package leanmapper-query
Lean Mapper Query
Lean Mapper Query is a concept of a query object for Lean Mapper library which helps to build complex queries using automatic joins (idea taken from NotORM library). Look at the suggested base classes. For Czech documentation have a look at the wiki.
Features
- behaves as a
SQL
preprocessor, hence most SQL expressions are available - automatic joins using the dot notation (
@book.tags.name
) - ability to query repositories or entities
- support for implicit filters
Installation
It can be installed via Composer.
What does it do?
Suppose we have the following repositories:
and the following entities:
We build a query:
Now, if we want to get all books whose author's name is Karel, we have to do this:
The database query will look like this:
You can see it performs automatic joins via the dot notation. It supports all relationship types known to Lean Mapper.
It is very easy to use SQL functions. We can update query like this:
which changes the database query into the following:
Don't repeat yourself
You can extend the Query
class and define your own methods.
Querying entities
It is also possible to query an entity property (currently only those properties with
BelongsToMany
or HasMany
relationships). Let's make the BaseEntity
class:
Note that BaseEntity
must extend LeanMapperQuery\Entity
to make the following possible.
We have defined the find
method as protected
because by specifying the method name in the
$magicMethodsPrefixes
property, you can query entities like this:
The magic method findTags
will eventually call your protected method find
with 'tags' as
the 1st argument.
The resulting database query looks like this:
The first condition in the where
clause, [tag].[id] IN (1, 2)
, is taken from the entity
traversing (tags are queried against this particular book entity's own tags).
What else you can do?
If we slightly modify BaseRepository
and BaseEntity
, we can simplify working with query objects.
To achieve this look at the suggested base classes. It makes
the following possible.
License
Copyright (c) 2013 Michal Bohuslávek
Licensed under the MIT license.