Queries: Difference between revisions

From Sunhill Framework Documentation
Restructured "Writing own queries"
Rewrite of Getting the records
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
Queries are a unified way to access different kinds of information of the Sunhill Framework. The query system is intended to be similar to database queries of laravel. The main difference is, that its possible to query entities that are not stored in a database.  
Queries are a unified way to access different kinds of information of the Sunhill Framework. The query system is intended to be similar to database queries of laravel. The main difference is, that its possible to query entities that are not stored in a database. All queries are performed on a [[Pooled record properies|Pooled record property]].  


== General usage ==
== General usage ==
All queries have to define some standardized methods. These are described in general in the following. For details see the different types of queries.
Due the fact that all queries are performed on pooled record properties, the searching process has to be performed by the storage. Normally it should be transparent to the user although there might be some missing functionallity in some features. Internally the queries use the [[Parser]]-subsystem. See [[Writing own queries]].  


== Common query functions ==
== Common query functions ==
Line 12: Line 12:
* '''records''' are all entities (or at least those that fit a certain criteria)
* '''records''' are all entities (or at least those that fit a certain criteria)


=== Finalizing calls ===
== Building a query ==
=== Finalizing call ==
All queries need a finalizing call, that indicates what information should be retrieved or what action should be performed.  
All queries need a finalizing call, that indicates what information should be retrieved or what action should be performed.  
=== Retrieving data ===
One main aspect of using queries is to retrieve data. Due the fact that queries are performed on pooled record properties there are always several ways to get data:


==== count() ====
==== count() ====
Line 27: Line 31:
returns the number of SampleEntity Records that have the name 'test'
returns the number of SampleEntity Records that have the name 'test'


==== A general note on first() and get() ====
==== Getting the records ====
===== first() =====
This method returns an instance of PooledRecordProperty and fills it with the fields of the first found record that matches the condition.
If not record exists it raises an exception.
 
===== firstIfExists() =====
Like first() it returns the first record matching the conditions. If none exists null is returned.
 
===== only() =====
This method expects excactly one result for the query. If there is none or more than one, an exception is raised.
 
===== get() =====
 
==== Getting the ids ====
===== firstID() =====
 
===== firstIDIfExists() =====
 
===== onlyID() =====
 
===== getIDs() =====
 
==== Getting the fields ====
When using the fields() statement in the query only these columns are returned when using first(), firstIfExists(), only() and get().
Note: When using firstID(), firstIDIfExists(), onlyID() and getIDs() with a fields() statement, the fields() statement is ignored and no warning is yielded.
 
Example:
SampleEntity::query()->fields('id')->first();
Returns for example 1
 
==== A general note on first(), firstIfExists(), only() and get() ====
===== Return type =====
===== Return type =====
first() and get() return the entity or a list of entities respectively. Normally a single entity is a StdClass with the givel columns as elements. In some cases it is useful to retun a different object.  
first() and get() return the entity or a list of entities respectively. Normally a single entity is a StdClass with the givel columns as elements. In some cases it is useful to retun a different object.  
Line 45: Line 79:
Returns {id: 1, name: 'test'}
Returns {id: 1, name: 'test'}


==== first() ====
==== first(?string|?array $column_list = null) ====
Returns the first record of the given query.  
Returns the first record of the given query.  


Line 62: Line 96:
Throws an exception when no record has the name 'non existing'.
Throws an exception when no record has the name 'non existing'.


== List of Queries ==
==== firstIfExists(?string|?array $column_list = null) ====
* [[ORM Query]]
Returns the first record of the given query or null if none exists.
* [[Classes Query]]
 
* [[Tags Query]]
{{Warning|When there is no <code>order()</code> statement, the result could be unpredictable.}}
* [[Attributes Query]]
 
* [[Properties Query]]
If the given query return no records at all null is returned.
 
Example:
SampleEntity::query()->first();
Returns the first record of SampleEntity.
 
SampleEntity::query()->where('name','test')->first();
Returns the first record of SampleEntity where the name is 'test';
 
SampleEntity::query()->where('name','not existing')->first();
Null is returned.
 
==== get(?string|?array $column_list = null) ====
Returns all entities that match the given condition.


== Writing own queries ==
==== only(?string|?array $column_list = null) ====
First check if you could use one of the predefined queries:
The query must return exactly one result and this result is returned. Same as first() except that it raises an exception when no or more than one result is returned.
* [[ArrayQuery]]
* [[DatabaseQuery]]


If not, your own queries have to be derrived from BasicQuery and some abstract methods have to be overwritten:
Example:
SampleEntity()::where('id','=',1)->only();


=== Methods ===
Returns the entity with the id 1 (or raises an exception when this id does not exist.
==== assembleQuery() ====
This method takes no parameters and builds an internal query structure that could be used to perform the finalizing methods on. The method can return whatever you want you just have to make sure that the remaining abstract methods can use this result to return the desired value or action.  


==== doGetCount($assembled_query) ====
==== delete() ====
This function takes the result of the previous function assembleQuery() and uses it to count the number of records that match the given criteria.  
Deletes all entries that match the given condition or throws an exception if the entity is read only.


==== doGet($assembled_query, $fields) ====
Example:
This function returns (depending on fields) all records or only certain fields that result of the $assmbled_query.
SampleEntity()::where('id','=',1)->delete();
{{Note|All elements of the Collection are automatically passed through the getRecord() method to return the standardized result, so you mustn't call getRecord() in the method doGet().}}


==== fieldExists(string $field): bool ====
Deletes the entity with the id 1.
Returns if the given $field exists as a field or a pseudo field.


==== fieldOrderable(string $field): bool ====
{{Note|If no entity matches the given condition nothing is done an no exception is raised}}
Returns if the given $field is usable as a sorting key in orderBy().


==== getRecord($record) ====
==== update(array $fields) ====
This method does not have to necessarily be overwritten. By default it just return $record. In some cases it is necessary to return another type (e.g. Object).
Updates all entries that match the given condition or throws an exception if the entity is read only.


=== Static data structures ===
Example:
SampleEntity()::where('id','=',1)->update(['payload'=>'abc']);


Sets the field ''payload'' to "abc" on the entity with the id 1 .


<!--
{{Note|If no entity matches the given condition nothing is done an no exception is raised}}


==== insert(array $fields) ====
Inserts a new record in the list.


=== Finishing methods ===
== List of Queries ==
Normally there must be a finishing method. All queries should define at least:
* [[ORM Query]]
* [[Classes Query]]
* [[Tags Query]]
* [[Attributes Query]]
* [[Properties Query]]
 
== Writing own queries ==
For details about writing own queries see [[Writing own queries|here]].  


==== count(): int ====
<!--
returns the count of entries that match a given condition


==== first() ====
Returns the first entry that match a given condition. This method should normally return a StdClass objects with the expcetion of object queries that return the appropriate object.


==== get(): Collection ====
Return all entries that match a given condition. The method returns an Illuminate\Support\Collection object. The entries of this collection are normally StdClasses with the exception of object queries that consist of the appropriate objects.


=== Query building ===
=== Query building ===
Line 119: Line 166:
==== where()/whereNot()/orWhere()/orWhereNot() ====
==== where()/whereNot()/orWhere()/orWhereNot() ====
The same method as the QueryBuilder of laravel provides. These methods can take up to three parameters (key, relation and value). If the last one is omitted it is assumed that the relation is "=" and the second parameter means the value (Example ->where('id',2) is the same as ->where('id','=',2)
The same method as the QueryBuilder of laravel provides. These methods can take up to three parameters (key, relation and value). If the last one is omitted it is assumed that the relation is "=" and the second parameter means the value (Example ->where('id',2) is the same as ->where('id','=',2)
==== offset(int $offset) ====
The same method as the QueryBuilder of laravel provides. The list starts with the $offet-th entry.
==== limit(int $limit) ====
The same method as the QueryBuilder of laravel provides. The list consists of $limit entries maximum.
==== order($key, $direction = 'asc') ====
The same method as the QueryBuilder of laravel provides. The list is ordered by $key in the direction $direction. $direction only may take 'asc' for ascending sort and 'desc' for descending.


== Classes::query() ==
== Classes::query() ==
Line 208: Line 246:
=== Fields/pseudo fields ===
=== Fields/pseudo fields ===
-->
-->
[[Category:Queries]]

Latest revision as of 13:32, 27 March 2025

Queries are a unified way to access different kinds of information of the Sunhill Framework. The query system is intended to be similar to database queries of laravel. The main difference is, that its possible to query entities that are not stored in a database. All queries are performed on a Pooled record property.

General usage

Due the fact that all queries are performed on pooled record properties, the searching process has to be performed by the storage. Normally it should be transparent to the user although there might be some missing functionallity in some features. Internally the queries use the Parser-subsystem. See Writing own queries.

Common query functions

As in QueryBuilder it is possible to build chains of request elements (like ->where('this','=','that')->orderBy('something')->offset(2)->limit(2)).

Terminology

Due the fact that queries could be performed on many entities there are some terms that are used:

  • record is a single entity (like a database entry, a tag, a class, a plugin, etc.)
  • records are all entities (or at least those that fit a certain criteria)

Building a query

= Finalizing call

All queries need a finalizing call, that indicates what information should be retrieved or what action should be performed.

Retrieving data

One main aspect of using queries is to retrieve data. Due the fact that queries are performed on pooled record properties there are always several ways to get data:

count()

Count returns the number of records of the given query.

Example:

SampleEntity::query()->count();

returns the number of all records of SampleEntity.

Example:

SampleEntity::query()->where('name','test')->count();

returns the number of SampleEntity Records that have the name 'test'

Getting the records

first()

This method returns an instance of PooledRecordProperty and fills it with the fields of the first found record that matches the condition. If not record exists it raises an exception.

firstIfExists()

Like first() it returns the first record matching the conditions. If none exists null is returned.

only()

This method expects excactly one result for the query. If there is none or more than one, an exception is raised.

get()

Getting the ids

firstID()
firstIDIfExists()
onlyID()
getIDs()

Getting the fields

When using the fields() statement in the query only these columns are returned when using first(), firstIfExists(), only() and get(). Note: When using firstID(), firstIDIfExists(), onlyID() and getIDs() with a fields() statement, the fields() statement is ignored and no warning is yielded.

Example:

SampleEntity::query()->fields('id')->first();

Returns for example 1

A general note on first(), firstIfExists(), only() and get()

Return type

first() and get() return the entity or a list of entities respectively. Normally a single entity is a StdClass with the givel columns as elements. In some cases it is useful to retun a different object.

Column list

There is an optional parameter $fields to first() that could either take a single string or an array of strings. If $fields is a string only the result of that field is returned.

Example:

SampleEntity::query()->first('id');

Returns for example 1

If $fields is an array of strings a StdClass object is returned where the elements represent the given fields.

Example:

SampleEntity::query()->first(['id','name']);

Returns {id: 1, name: 'test'}

first(?string|?array $column_list = null)

Returns the first record of the given query.

Warning: When there is no order() statement, the result could be unpredictable.

If the given query return no records at all an exception is raised.

Example:

SampleEntity::query()->first();

Returns the first record of SampleEntity.

SampleEntity::query()->where('name','test')->first();

Returns the first record of SampleEntity where the name is 'test';

SampleEntity::query()->where('name','not existing')->first();

Throws an exception when no record has the name 'non existing'.

firstIfExists(?string|?array $column_list = null)

Returns the first record of the given query or null if none exists.

Warning: When there is no order() statement, the result could be unpredictable.

If the given query return no records at all null is returned.

Example:

SampleEntity::query()->first();

Returns the first record of SampleEntity.

SampleEntity::query()->where('name','test')->first();

Returns the first record of SampleEntity where the name is 'test';

SampleEntity::query()->where('name','not existing')->first();

Null is returned.

get(?string|?array $column_list = null)

Returns all entities that match the given condition.

only(?string|?array $column_list = null)

The query must return exactly one result and this result is returned. Same as first() except that it raises an exception when no or more than one result is returned.

Example:

SampleEntity()::where('id','=',1)->only();

Returns the entity with the id 1 (or raises an exception when this id does not exist.

delete()

Deletes all entries that match the given condition or throws an exception if the entity is read only.

Example:

SampleEntity()::where('id','=',1)->delete();

Deletes the entity with the id 1.

Note: If no entity matches the given condition nothing is done an no exception is raised

update(array $fields)

Updates all entries that match the given condition or throws an exception if the entity is read only.

Example:

SampleEntity()::where('id','=',1)->update(['payload'=>'abc']);

Sets the field payload to "abc" on the entity with the id 1 .

Note: If no entity matches the given condition nothing is done an no exception is raised

insert(array $fields)

Inserts a new record in the list.

List of Queries

Writing own queries

For details about writing own queries see here.