The TSV format doesn't currently properly escape the \ character; a value of \t can thus not be correctly returned. The \r character should also be escaped.
The CSV format queries and acts on a header URL attribute, but this is currently neither supported, nor documented or properly tested (though it is misleadingly used in testing). Alternatively, we could consider adding this as a feature, in line with what other RDBMs are doing (Postgresql, SSRS etc).
(This could potentially also allow for a more unequivocal naming of the hasHeader method deciding in fact if the response should contain the columns' headers.)
The TSV format doesn't currently properly escape the
\
character; a value of\t
can thus not be correctly returned. The\r
character should also be escaped.The CSV format queries and acts on a
header
URL attribute, but this is currently neither supported, nor documented or properly tested (though it is misleadingly used in testing). Alternatively, we could consider adding this as a feature, in line with what other RDBMs are doing (Postgresql, SSRS etc). (This could potentially also allow for a more unequivocal naming of thehasHeader
method deciding in fact if the response should contain the columns' headers.)