TAP-1.1 columns.column_index info

[Marco Molinaro]

Dear DAL/Apps-ers,
in updating the TASMAN TAP_SCHEMA manager application,
on the way to let the app user decide the column ordering
(i.e. filling up the TAP_SCHEMA.columns.column_index values)
we are going the following way: let the user define ordering on
the important/preferred columns while leaving "unordered" the
other columns.

That is: we may have a bunch of NULLs alongside integers as the
column_index values.

TAP-1.1 latest revision is not preventing this.
My only question is: will applications be OK with this?

The intent is to have the NULL-annotated-column_index
columns fall (potentially) unordered after the ordered
ones when rendered into the client.

Comments?

Cheers,
    Marco
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ivoa.net/pipermail/apps/attachments/20180112/3f3292e2/attachment.html>