You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All the INTEGER.getArrayDataType().getArrayDataType() calls generated for multi dimensional arrays (#252) are a bit unwieldy. We have a couple of convenience methods on DataType that correspond more to SQL syntax, such as null_() and notNull(), which represent the historic versions like nullable(true). Would certainly make sense to introduce array() as well for this purpose, to get INTEGER.array().array()
The text was updated successfully, but these errors were encountered:
This includes:
- [#14406] The AutoAlias feature isn't applied from within the JOIN tree, only from the TableList
- Update AutoAlias to allow for auto-aliasing other tables than this
- Add NoAutoAlias to prevent aliasing in derived column list emulations
- Removed TableWithOrdinalityStep again, all Table types are supported
- Implement emulations
- Added an AbstractAutoAliasTable base implementation for AliasTable
- [#14409] Refactor Values to implement AutoAlias
- [#13971] Use DataType::array internally
- [#14388] Fix data type of ArrayConcat expression
All the
INTEGER.getArrayDataType().getArrayDataType()
calls generated for multi dimensional arrays (#252) are a bit unwieldy. We have a couple of convenience methods onDataType
that correspond more to SQL syntax, such asnull_()
andnotNull()
, which represent the historic versions likenullable(true)
. Would certainly make sense to introducearray()
as well for this purpose, to getINTEGER.array().array()
The text was updated successfully, but these errors were encountered: