diff --git a/en/reference/native-sql.rst b/en/reference/native-sql.rst
index b1d0740c2..477297485 100644
--- a/en/reference/native-sql.rst
+++ b/en/reference/native-sql.rst
@@ -394,3 +394,477 @@ For entites with more columns the builder is very convenient to use. It extends
and as such has all the functionality of it as well. Currently the ``ResultSetMappingBuilder`` does not support
entities with inheritance.
+
+Named Native Query
+------------------
+
+You can also map a native query using a named native query mapping.
+
+To achieve that, you must describe the SQL resultset structure
+using named native query (and sql resultset mappings if is a several resultset mappings).
+
+Like named query, a named native query can be defined at class level or in a XML or YAML file.
+
+
+A resultSetMapping parameter is defined in @NamedNativeQuery,
+it represents the name of a defined @SqlResultSetMapping.
+
+.. configuration-block::
+
+ .. code-block:: php
+
+
+
+
+
+ SELECT u.id AS u_id, u.name AS u_name, u.status AS u_status, a.id AS a_id, a.zip AS a_zip, a.country AS a_country, COUNT(p.phonenumber) AS numphones FROM users u INNER JOIN addresses a ON u.id = a.user_id INNER JOIN phonenumbers p ON u.id = p.user_id GROUP BY u.id, u.name, u.status, u.username, a.id, a.zip, a.country ORDER BY u.username
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ .. code-block:: yaml
+
+ MyProject\Model\User:
+ type: entity
+ namedNativeQueries:
+ fetchMultipleJoinsEntityResults:
+ name: fetchMultipleJoinsEntityResults
+ resultSetMapping: mappingMultipleJoinsEntityResults
+ query: SELECT u.id AS u_id, u.name AS u_name, u.status AS u_status, a.id AS a_id, a.zip AS a_zip, a.country AS a_country, COUNT(p.phonenumber) AS numphones FROM users u INNER JOIN addresses a ON u.id = a.user_id INNER JOIN phonenumbers p ON u.id = p.user_id GROUP BY u.id, u.name, u.status, u.username, a.id, a.zip, a.country ORDER BY u.username
+ sqlResultSetMappings:
+ mappingMultipleJoinsEntityResults:
+ name: mappingMultipleJoinsEntityResults
+ columnResult:
+ 0:
+ name: numphones
+ entityResult:
+ 0:
+ entityClass: __CLASS__
+ fieldResult:
+ 0:
+ name: id
+ column: u_id
+ 1:
+ name: name
+ column: u_name
+ 2:
+ name: status
+ column: u_status
+ 1:
+ entityClass: Address
+ fieldResult:
+ 0:
+ name: id
+ column: a_id
+ 1:
+ name: zip
+ column: a_zip
+ 2:
+ name: country
+ column: a_country
+
+
+Things to note:
+ - The resultset mapping declares the entities retrieved by this native query.
+ - Each field of the entity is bound to an SQL alias (or column name).
+ - All fields of the entity including the ones of subclasses
+ and the foreign key columns of related entities have to be present in the SQL query.
+ - Field definitions are optional provided that they map to the same
+ column name as the one declared on the class property.
+ - ``__CLASS__`` is a alias for the mapped class
+
+
+In the above example,
+the ``fetchJoinedAddress`` named query use the joinMapping result set mapping.
+This mapping returns 2 entities, User and Address, each property is declared and associated to a column name,
+actually the column name retrieved by the query.
+
+Let's now see an implicit declaration of the property / column.
+
+.. configuration-block::
+
+ .. code-block:: php
+
+
+
+
+
+ SELECT * FROM addresses
+
+
+
+
+
+
+
+
+
+ .. code-block:: yaml
+
+ MyProject\Model\Address:
+ type: entity
+ namedNativeQueries:
+ findAll:
+ resultSetMapping: mappingFindAll
+ query: SELECT * FROM addresses
+ sqlResultSetMappings:
+ mappingFindAll:
+ name: mappingFindAll
+ entityResult:
+ address:
+ entityClass: Address
+
+
+In this example, we only describe the entity member of the result set mapping.
+The property / column mappings is done using the entity mapping values.
+In this case the model property is bound to the model_txt column.
+If the association to a related entity involve a composite primary key,
+a @FieldResult element should be used for each foreign key column.
+The @FieldResult name is composed of the property name for the relationship,
+followed by a dot ("."), followed by the name or the field or property of the primary key.
+
+
+.. configuration-block::
+
+ .. code-block:: php
+
+
+
+
+
+ SELECT u.id, u.name, u.status, a.id AS a_id, a.country AS a_country, a.zip AS a_zip, a.city AS a_city FROM users u INNER JOIN addresses a ON u.id = a.user_id WHERE u.username = ?
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ .. code-block:: yaml
+
+ MyProject\Model\User:
+ type: entity
+ namedNativeQueries:
+ fetchJoinedAddress:
+ name: fetchJoinedAddress
+ resultSetMapping: mappingJoinedAddress
+ query: SELECT u.id, u.name, u.status, a.id AS a_id, a.country AS a_country, a.zip AS a_zip, a.city AS a_city FROM users u INNER JOIN addresses a ON u.id = a.user_id WHERE u.username = ?
+ sqlResultSetMappings:
+ mappingJoinedAddress:
+ entityResult:
+ 0:
+ entityClass: __CLASS__
+ fieldResult:
+ 0:
+ name: id
+ 1:
+ name: name
+ 2:
+ name: status
+ 3:
+ name: address.id
+ column: a_id
+ 4:
+ name: address.zip
+ column: a_zip
+ 5:
+ name: address.city
+ column: a_city
+ 6:
+ name: address.country
+ column: a_country
+
+
+
+If you retrieve a single entity and if you use the default mapping,
+you can use the resultClass attribute instead of resultSetMapping:
+
+.. configuration-block::
+
+ .. code-block:: php
+
+
+
+
+
+ SELECT * FROM addresses WHERE id = ?
+
+
+
+
+ .. code-block:: yaml
+
+ MyProject\Model\Address:
+ type: entity
+ namedNativeQueries:
+ findAll:
+ name: findAll
+ resultClass: Address
+ query: SELECT * FROM addresses
+
+
+In some of your native queries, you'll have to return scalar values,
+for example when building report queries.
+You can map them in the @SqlResultsetMapping through @ColumnResult.
+You actually can even mix, entities and scalar returns in the same native query (this is probably not that common though).
+
+.. configuration-block::
+
+ .. code-block:: php
+
+
+
+
+ SELECT COUNT(*) AS count FROM addresses
+
+
+
+
+
+
+
+
+ .. code-block:: yaml
+
+ MyProject\Model\Address:
+ type: entity
+ namedNativeQueries:
+ count:
+ name: count
+ resultSetMapping: mappingCount
+ query: SELECT COUNT(*) AS count FROM addresses
+ sqlResultSetMappings:
+ mappingCount:
+ name: mappingCount
+ columnResult:
+ count:
+ name: count
\ No newline at end of file