> A small add-on info: with SDSS, people are routinely requesting output
> tables containing over 10 million rows. This is the typical size that we
> should be worried about, not tables with 100-1000 rows.
Yes, agreed...
> I like Guy's suggestion, that would avoid any conflicts with streaming.
While I was wavering, I've now been convinced that Guy's suggestion doesn't help because to get to the meta-data you'd have had to parse the entire TABLEDATA element anyway.
So my current vote is an optional attribute to TABLEDATA, after all the number of rows in a TABLEDATA should be associated as closely as possible with the TABLEDATA itself? Putting it in an element "elsewhere" looses that association.
Of course this doesn't help you in the streaming case, but with a streaming table you've committed yourself to parse the entire thing anyway so you wouldn't be paying any attention to the tag anyway...
Al. Received on 2003-10-23Z14:51:58