GROUP BY ROLLUP(column,column.) and GROUP B CUBE(column,column.) are now supported.type_=(“hbar”|“stackedbar“ | “hstackedbar“|“percentbar“|“hpercentbar“). Also, supplementing the existing type:datehms24 as a format type for timestamps (date+time values), it is now possible to specify type:datehms12, type:date4yhms24, and type:date4yhms12. The dec: option specifies the number of digits shown after the decimal place for seconds, and defaults to 0. Also, the format string attribute type:days specifies that a floating-point value is to be construed as a day-to-second interval representing a possibly fractional number of days and displayed broken down as days, hours, minutes, and (possibly fractional) seconds. The format string attribute type:months may now be used to specify that an integer value is to be construed as a year-to-month interval representing a whole number of months and displayed broken down as years and months.The currently valid values of locale are US, UK, EU, and INT other locale specifications may be added in the future. The format string option locale: may now be used to modify the display behavior for numeric, date, and date+time values, overriding user preferences.Furthermore, a negative value for padto: specifies padding on the right. Alternatively, padto: may also be specified, in which case the value may be padded to fewer characters than the full column width. The format string option padwith: may now be used along with numeric (such as num, commas, pct, currency) and text (char) formats (not date/time etc.) to specify that the displayed value should filled or "padded" out to the column width with a particular character or sequence.There is also an /api/aqi/.qlog widget that exposes this same data as a table, allowing things like /api/aqi/.qlog/!data:json.rows?sort_=reqid, etc. Data is returned as a dictionary of columns. Added commands get_qlog and clear_qlog to get a tabular query system that tracks when each query was sent to AQI, when it was sent to a worker (which may be sometime later if all workers were busy and the request got queued), and when the data came back from the worker.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |