What does your feature request improve on? Please describe.
Storing image data in columns is although most of the time only 1 byte per channel now quite memory intense. Would be better, if it is possible to also support other data types like int and so.
Describe the solution you'd like
Enable other data types implicitly used via image and data loading and explicitly used e.g. via TAB().convert(..., "value-TYPE")
Additional context
Add any other context or screenshots about the feature request here.
(Do not write below this line)
DEVS' SECTION
ANALYSIS
Seems not to be too difficult. Requires some remaining decisions, i.e. how to represent the columns as code (using a template for example), and how to determine their type. File IO should not be negatively affected. Would, however, be nice, if the function for reading a column would warn the user, if a column cannot be interpreted.
DESCRIPTION
What does your feature request improve on? Please describe. Storing image data in columns is although most of the time only 1 byte per channel now quite memory intense. Would be better, if it is possible to also support other data types like
intand so.Describe the solution you'd like Enable other data types implicitly used via image and data loading and explicitly used e.g. via
TAB().convert(..., "value-TYPE")Additional context Add any other context or screenshots about the feature request here.
(Do not write below this line)
DEVS' SECTION
ANALYSIS
Seems not to be too difficult. Requires some remaining decisions, i.e. how to represent the columns as code (using a template for example), and how to determine their type. File IO should not be negatively affected. Would, however, be nice, if the function for reading a column would warn the user, if a column cannot be interpreted.
IMPLEMENTATION STEPS
(see also our Wiki for implementation guidelines)
DOCUMENTATION STEPS
(see also our Wiki for further information)
*.NHLPand*.NDBfiles, if needed)*.NLNGfiles, if needed)PULL REQUEST