> For the complete documentation index, see [llms.txt](https://bxorm.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bxorm.ortusbooks.com/bxorm-2.x/getting-started/configuration/naming-strategies.md).

# Naming Strategies

Control how entity and property names become table and column names

Boxlang ORM provides flexible naming strategies to control how entity and property names are mapped to database tables and columns. This allows you to easily customize schema, table, column and other physical names to match your database conventions without having to change your source code.

## Predefined Naming Strategies

You have several choices of naming strategies to choose from:

* **default**: No conversion is performed. Entity and property names are mapped to table and column names exactly as defined in your code.
* **smart**: Applies a smart conversion:
  * All names are forced to uppercase.
  * camelCase names are automatically separated with underscores. For example, `userProfile` becomes `USER_PROFILE`.
* **custom**: Specify a custom naming strategy class that implements the `INamingStrategy` interface. This allows you to implement your own logic for converting names. See [Custom Naming Strategy](#custom-naming-strategy).

## Custom Naming Strategy

Need something else? Try a custom naming strategy. This allows you to implement your own logic for converting entity and property names to table and column names.

```js
this.ormSettings = {
	// ...
	namingStrategy : "models.orm.UnderscoreNamingStrategy"
}
```

The naming strategy may implement [the `INamingStrategy` interface](https://github.com/ortus-boxlang/bx-orm/blob/development/src/main/bx/models/INamingStrategy.bx#L23), or you may omit the declaration and simply provide a class with the appropriate methods. The following methods are supported:

* `public string function getTableName( string tableName )`
* `public string function getColumnName( string columnName )`
* `public string function getCatalogName( string catalogName )`
* `public string function getSchemaName( string schemaName )`
* `public string function getSequenceName( string sequenceName )`


---

# 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://bxorm.ortusbooks.com/bxorm-2.x/getting-started/configuration/naming-strategies.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.