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
Here are some reasons that why we need these fields now:
Encoding and decoding: datatype is needed to decode from wal, and is_nullable is used to decide whether to cast to Option
Bindings:
Bindings can use name to identify columns. If we remove name, We need to ensure that the order of columns(getting from tonbo) is the same as the order defined by the schema, and we should set name for every column that is to return to user
Bindings use datatype to convert the value to the corresponding value, we can use column description though
The text was updated successfully, but these errors were encountered:
Column
need a lot of information that can be found inColumnDesc
. Is there an elegant way to remove these fields?Here are some reasons that why we need these fields now:
datatype
is needed to decode from wal, andis_nullable
is used to decide whether to cast toOption
name
to identify columns. If we removename
, We need to ensure that the order of columns(getting from tonbo) is the same as the order defined by the schema, and we should setname
for every column that is to return to userdatatype
to convert the value to the corresponding value, we can use column description thoughThe text was updated successfully, but these errors were encountered: