# 0.45.0 - March 2025

This release introduced a few breaking changes related to **custom resolver sequences**. If you do not override standard SnowDDL classes and resolver sequences, nothing should change.

### Changes

* Separated `DatabaseAccessRoleResolver` into:
  *  `DatabaseOwnerRoleResolver`
  *  `DatabaseReadRoleResolver`
  *  `DatabaseWriteRoleResolver`
* Separated `SchemaAccessRoleResolver` into:
  * `SchemaOwnerRoleResolver`
  * `SchemaReadRoleResolver`
  * `SchemaWriteRoleResolver`
* Separated `WarehouseAccessRoleResolver` into:
  * `WarehouseMonitorRoleResolver` 
  * `WarehouseUsageRoleResolver`

### How to adapt resolver sequences?

Find:

<pre><code><strong>    DatabaseAccessRoleResolver,
</strong>    SchemaAccessRoleResolver, 
</code></pre>

Replace with:

```
    DatabaseReadRoleResolver,
    DatabaseWriteRoleResolver,
    SchemaReadRoleResolver,
    SchemaWriteRoleResolver,
    DatabaseOwnerRoleResolver,
    SchemaOwnerRoleResolver,
```

"Owner" roles should always be processed AFTER "read" and "write" roles.

\---

Find:

```
    WarehouseAccessRoleResolver,
```

Replace with:

```
    WarehouseMonitorRoleResolver,
    WarehouseUsageRoleResolver,
```

This changes was made in order to unify code for objects with multiple role types.

### Using owner\_schema\_\* parameters for DATABASE object type

It is now possible to define `owner_schema_read` and `owner_schema_write` for [DATABASE](/basic/yaml-configs/database.md) object type. Previously these parameters were not available due to resolver execution order.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.snowddl.com/breaking-changes-log/0.45.0-march-2025.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.