Found while working on issue #2407 / [sc-51048]. See also [sc-55657].

Python

The SOMADataFrame create method accepts domain here:

• TileDB-SOMA/apis/python/src/tiledbsoma/_dataframe.py

  Line 138 in 248f46e

  domain: Optional[Domain] = None,

• TileDB-SOMA/apis/python/src/tiledbsoma/_dataframe.py

  Lines 156 to 167 in 248f46e

  	domain:
  	An optional sequence of tuples specifying the domain of each
  	index column. Each tuple should be a pair consisting of the minimum and
  	maximum values storable in the index column. For example, if there is a
  	single int64-valued index column, then ``domain`` might be ``[(100,
  	200)]`` to indicate that values between 100 and 200, inclusive, can be
  	stored in that column. If provided, this sequence must have the same
  	length as ``index_column_names``, and the index-column domain will be as
  	specified. If omitted entirely, or if ``None`` in a given dimension,
  	the corresponding index-column domain will use the minimum and maximum
  	possible values for the column's datatype. This makes a
  	:class:`DataFrame` growable.

R

The SOMADataFrame create method does not accept domain here:

• TileDB-SOMA/apis/r/R/SOMADataFrame.R

  Lines 26 to 31 in 248f46e

  	create = function(
  	schema,
  	index_column_names = c("soma_joinid"),
  	platform_config = NULL,
  	internal_use_only = NULL
  	) {

For this reason, here

calling here

the domain is taken from the datatype's max range.

This is a R/Python parity issue which will become noticeable on #2407 and should be prioritized.