> For the complete documentation index, see [llms.txt](https://coldbox-orm.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coldbox-orm.ortusbooks.com/v5.x/base-orm-service/service-methods/finders/findall.md).

# findAll

Find all the entities for the specified HQL query and its named or positional parameters.

## Returns

* This function returns *array*
* This function returns a Java `Stream` if **asStream = true** (see [Java Streams](/v5.x/advanced/java-streams.md))

## Arguments

| Key        | Type    | Required | Default            | Description                                 |
| ---------- | ------- | -------- | ------------------ | ------------------------------------------- |
| query      | string  | No       | ---                | The HQL Query to execute                    |
| params     | any     | No       | `{}`               | Named (struct) or positional (array) params |
| offset     | numeric | No       | 0                  | Pagination offset                           |
| max        | numeric | No       | 0                  | Max records to return                       |
| timeout    | numeric | No       | 0                  | Query timeout                               |
| ignoreCase | boolean | No       | false              | Ignored, kept for compatibility             |
| datasource | string  | No       | Service datasource | The datasource to use                       |
| asStream   | boolean | No       | false              | Returns a Java `Stream` instead of an array |
| options    | struct  | No       | `{}`               | More `bx-orm` `ormExecuteQuery()` options   |

{% hint style="info" %}
Positional parameters can be written as plain `?` or numbered `?1`, `?2` (JPA style). Named parameters use `:name`. Entity and property names in the HQL can be in any case: `bx-orm` resolves them.
{% endhint %}

## Examples

```javascript
// find all blog posts
ormService.findAll( "from Post" );
// with a positional parameters
ormService.findAll( "from Post as p where p.author=?", [ 'Luis Majano' ] );
// 10 posts from Luis Majano starting from 5th post ordered by release date
ormService.findAll( "from Post as p where p.author=?1 order by p.releaseDate", [ 'Luis Majano' ], offset=5, max=10 );

// Using paging params
var query = "from Post as p where p.author='Luis Majano' order by p.releaseDate"
// first 20 posts
ormService.findAll( query=query, max=20 )
// 20 posts starting from my 15th entry
ormService.findAll( query=query, max=20, offset=15 );

// examples with named parameters
ormService.findAll( "from Post as p where p.author=:author", { author='Luis Majano' } )
ormService.findAll( "from Post as p where p.author=:author", { author='Luis Majano' }, max=20, offset=5 );
```

If you want to query by example, use [`findByExample()`](/v5.x/base-orm-service/service-methods/finders/findbyexample.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://coldbox-orm.ortusbooks.com/v5.x/base-orm-service/service-methods/finders/findall.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.