DYNAMIC RESULT SETS RETURNED dynamic_result_sets_returned 01008 IMPLICIT ZERO BIT PADDING implicit_zero_bit_padding 01003 NULL VALUE ELIMINATED IN SET FUNCTION null_value_eliminated_in_set_function data type CHAR is not recommended. In Greenplum Database, the data types VARCHAR or TEXT handle padding added to the data (space characters added after the last non-space character) as significant characters -1 indicates a NULL field value. No value bytes follow in the NULL case. There is no alignment padding or any other extra data between fields. Presently, all data values in a binary-format file are assumed

DYNAMIC RESULT SETS RETURNED dynamic_result_sets_returned 01008 IMPLICIT ZERO BIT PADDING implicit_zero_bit_padding 01003 NULL VALUE ELIMINATED IN SET FUNCTION null_value_eliminated_in_set_function data type CHAR is not recommended. In Greenplum Database, the data types VARCHAR or TEXT handle padding added to the data (space characters added after the last non-space character) as significant characters -1 indicates a NULL field value. No value bytes follow in the NULL case. There is no alignment padding or any other extra data between fields. Presently, all data values in a binary-format file are assumed

DYNAMIC RESULT SETS RETURNED dynamic_result_sets_returned 01008 IMPLICIT ZERO BIT PADDING implicit_zero_bit_padding 01003 NULL VALUE ELIMINATED IN SET FUNCTION null_value_eliminated_in_set_function data type CHAR is not recommended. In Greenplum Database, the data types VARCHAR or TEXT handle padding added to the data (space characters added after the last non-space character) as significant characters -1 indicates a NULL field value. No value bytes follow in the NULL case. There is no alignment padding or any other extra data between fields. Presently, all data values in a binary-format file are assumed

DYNAMIC RESULT SETS RETURNED dynamic_result_sets_returned 01008 IMPLICIT ZERO BIT PADDING implicit_zero_bit_padding 01003 NULL VALUE ELIMINATED IN SET FUNCTION null_value_eliminated_in_set_fu nction data type CHAR is not recommended. In Greenplum Database, the data types VARCHAR or TEXT handle padding added to the data (space characters added after the last non-space character) as significant characters -1 indicates a NULL field value. No value bytes follow in the NULL case. There is no alignment padding or any other extra data between fields. Presently, all data values in a binary-format file are assumed

data type CHAR is not recommended. In Greenplum Database, the data types VARCHAR or TEXT handle padding added to the data (space characters added after the last non-space character) as significant characters DYNAMIC RESULT SETS RETURNED dynamic_result_sets_returned 01008 IMPLICIT ZERO BIT PADDING implicit_zero_bit_padding 01003 NULL VALUE ELIMINATED IN SET FUNCTION null_value_eliminated_in_set_fu nction -1 indicates a NULL field value. No value bytes follow in the NULL case. There is no alignment padding or any other extra data between fields. Presently, all data values in a binary-format file are assumed

data type CHAR is not recommended. In Greenplum Database, the data types VARCHAR or TEXT handle padding added to the data (space characters added after the last non-space character) as significant characters DYNAMIC RESULT SETS RETURNED dynamic_result_sets_returned 01008 IMPLICIT ZERO BIT PADDING implicit_zero_bit_padding 01003 NULL VALUE ELIMINATED IN SET FUNCTION null_value_eliminated_in_set_function -1 indicates a NULL field value. No value bytes follow in the NULL case. There is no alignment padding or any other extra data between fields. Presently, all data values in a binary-format file are assumed

data type CHAR is not recommended. In Greenplum Database, the data types VARCHAR or TEXT handle padding added to the data (space characters added after the last non-space character) as significant characters DYNAMIC RESULT SETS RETURNED dynamic_result_sets_returned 01008 IMPLICIT ZERO BIT PADDING implicit_zero_bit_padding 01003 NULL VALUE ELIMINATED IN SET FUNCTION null_value_eliminated_in_set_ function -1 indicates a NULL field value. No value bytes follow in the NULL case. There is no alignment padding or any other extra data between fields. Presently, all data values in a binary-format file are assumed

data type CHAR is not recommended. In Greenplum Database, the data types VARCHAR or TEXT handle padding added to the data (space characters added after the last non-space character) as significant characters DYNAMIC RESULT SETS RETURNED dynamic_result_sets_returned 01008 IMPLICIT ZERO BIT PADDING implicit_zero_bit_padding 01003 NULL VALUE ELIMINATED IN SET FUNCTION null_value_eliminated_in_set_ function -1 indicates a NULL field value. No value bytes follow in the NULL case. There is no alignment padding or any other extra data between fields. Presently, all data values in a binary-format file are assumed

data type CHAR is not recommended. In Greenplum Database, the data types VARCHAR or TEXT handle padding added to the data (space characters added after the last non-space character) as significant characters DYNAMIC RESULT SETS RETURNED dynamic_result_sets_returned 01008 IMPLICIT ZERO BIT PADDING implicit_zero_bit_padding 01003 NULL VALUE ELIMINATED IN SET FUNCTION null_value_eliminated_in_set_fu nction -1 indicates a NULL field value. No value bytes follow in the NULL case. There is no alignment padding or any other extra data between fields. Presently, all data values in a binary-format file are assumed

data type CHAR is not recommended. In Greenplum Database, the data types VARCHAR or TEXT handle padding added to the data (space characters added after the last non-space character) as significant characters DYNAMIC RESULT SETS RETURNED dynamic_result_sets_returned 01008 IMPLICIT ZERO BIT PADDING implicit_zero_bit_padding 01003 NULL VALUE ELIMINATED IN SET FUNCTION null_value_eliminated_in_set_fu nction -1 indicates a NULL field value. No value bytes follow in the NULL case. There is no alignment padding or any other extra data between fields. Presently, all data values in a binary-format file are assumed