> For the complete documentation index, see [llms.txt](https://doc.telosys.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.telosys.org/target-sql-scripts/type-size-and-precision.md).

# Type size and precision

### Type size

The "**size**" is often required for SQL types like:

* CHAR(size)
* VARCHAR(size)
* VARCHAR2(size)
* NVARCHAR(size)
* BINARY(size)
* VARBINARY(size)

This is how the size value is determined:

1. if the attribute has a "**@DbType**" annotation this database type will be used "as is"\
   regardless of the target database\
   Example:\
       `name : string {`` `**`@DbType('VARCHAR(20)')`**`  ``}`\
   the SQL type will be **`VARCHAR(20)`**
2. else  if the attribute has a "**@Size**" annotation this value will be used \
   Example: \
       `name : string {`` `**`@Size(20)`**`}`\
   the SQL type will be \
     \- **`VARCHAR(20)`** for PostgreSQL \
     \- **`VARCHAR2(20)`** for Oracle
3. else  if the attribute has a "**@MaxLen**" annotation this value will be used \
   Example:\
       `name : string {`` `**`@MaxLen(12)`**`}`\
   the SQL type will be \
     \- **`VARCHAR(12)`**  for PostgreSQL \
     \- **`VARCHAR2(12)`** for Oracle
4. else  if the size is not mandatory ("%s") for the SQL type\
   then the type is generated without size, for example:\
     \- **`VARCHAR`**  for PostgreSQL 
5. else  size is mandatory ("%S") and cannot be determined:\
   an error is thrown

Reminder: "*@DbSize(xx)*" annotation is deprecated (do  not use it)

### Type precision 

The "**precision**" is often required (or indispensable) for SQL types like:

* NUMERIC(precision) 
* NUMBER(precision) 
* DECIMAL(precision)
* FLOAT(precision)

The "**precision**" defines the number of digits for a decimal type, \
it can contains a "**scale**" (number of digits after the decimal).

Examples: 

* "10"  :  precision = 10 digits
* "8,2"  :  precision = 8 digits with 2 digits after the decimal (scale = 2)

This is how the precision value is determined:

1. if the attribute has a "**@DbType**" annotation this database type will be used "as is"\
   regardless of the target database\
   Example:\
       `weight : decimal {`` `**`@DbType('DECIMAL(5,2)')`**` ``}`\
   the SQL type will be  **`DECIMAL(5,2)`**
2. else  if the attribute has a "**@Size**" annotation this value will be used \
   Example: \
       `weight: decimal {`` `**`@Size(8,5)`**` ``}`\
   the SQL type will be \
     \- **numeric(8,5)**   for PostgreSQL \
     \- **NUMBER(8,5)**   for Oracle
3. else  if the attribute has a "**@MaxLen**" annotation this value will be used \
   Example:\
       `weight : decimal {`` `**`@MaxLen(12)`**` ``}`\
   the SQL type will be \
     \- **`numeric(12)`** for PostgreSQL \
     \- **`NUMBER(12)`** for Oracle
4. else  if the precision is not mandatory ("%p") for the SQL type\
   then the type is generated without precision, for example:\
     \- **`numeric`**  for PostgreSQL \
     \- **`NUMBER` ** for Oracle 
5. else  precision is mandatory ("%P") and cannot be determined:\
   an error is thrown<br>

Reminder: "*@DbSize(xx)*" annotation is deprecated (do  not use it)


---

# 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 dynamically by asking a question.

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

```
GET https://doc.telosys.org/target-sql-scripts/type-size-and-precision.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.