Restrictions on Partition Keys and Bound Values for Range-Partitioned Tables

Partition bounds must be in ascending order according to the order in which the partitions were created. That is, the upper bound for the second partition must be higher than for the first partition, and so on.

In addition, partition bound values must be compatible with the corresponding partition-key column datatype. For example, varchar is compatible with char. If a bound value has a different datatype than that of its corresponding partition-key column, SAP ASE converts the bound value to the datatype of the partition-key column, with these exceptions:

Explicit conversions are not allowed. This example attempts an illegal conversion from varchar to int:

create table employees(emp_names varchar(20)) 
			partition by range(emp_name)
		(p1 values <=(1),
		p2 values <= (10))

Implicit conversions that result in data loss are not allowed. In this example, rounding assumptions may lead to data loss if SAP ASE converts the bound values to integer values. The partition bounds are not compatible with the partition-key datatype.
```
create table emp_id (id int)
			partition by range(id)
		(p1 values <= (10.5),
		p2 values <= (100.5))
```
In this example, the partitions bounds and the partition-key datatype are compatible. SAP ASE converts the bound values directly to float values. No rounding is required, and conversion is supported.
```
create table id_emp (id float)
			partition by range(id)
		(p1 values <= (10),
		p2 values <= (100))
```
Conversions from nonbinary datatypes to binary datatypes are not allowed. For example, this conversion is not allowed:
```
create table newemp (name binary)
			partition by range(name)
		(p1 values <= (“Maarten”),
		p2 values <= (“Zymmerman”)) 
```