Gregory Dubois-Felsmann added a comment - 08/Jun/18 2:50 PM Is this available on a Kubernetes build?

Loi Ly added a comment - 08/Jun/18 3:30 PM Gregory Dubois-Felsmann , https://irsawebdev9.ipac.caltech.edu/dm-13382/firefly/

Gregory Dubois-Felsmann added a comment - 21/Jun/18 10:04 AM I can't view this in Safari because of the self-signed certificate. I haven't figured out how to work around that - recent versions of Safari don't offer an obvious path to accept the certificate. Attempting to view it in Firefox caused a fresh copy of Firefox 60.0.2 to crash while loading the results of a query. I have never seen this happen before with Firefly that I can recall. Upon reloading, the crash did not re-occur. In a table result, the vertical spacing between the column name, the units (in parentheses) and the data type is very cramped. See attachment. I would suggest adding a pixel or two. Now that we are making these names public, I wonder if "string" would be preferable to "char", which has some complicated implications for people with a C background. (In that context, I would ask: what kind of strings are these? 7-bit ASCII? 8-bit ISO-Latin-1? Unicode?) It is odd that the data types are not displayed in the "Table Options" dialog along with the units. I think this should be fixed. I am much more likely to want to just occasionally look up the data type in this dialog than I am to want to permanently commit screen real estate to putting it in the header, in fact. It is also odd, from a user perspective, that there is a completely different "dbtype" in the table schema layout on the query screen, not at all the same as the "data type" we are now displaying. I understand the historical reason for the discrepancy - "dbtype" is a formal SQL database data type, versus "data type" being a Firefly concept. Now that we use a database internally for tables, what are the actual database data types used internally that correspond to the old "data type" strings? Pending the answer to that, I don't have a good suggestion for an improvement in this area right now. It is part of a "cognitive style" in which Firefly tends to expose technical implementation details, though, and I'd like to continue thinking about it.

Xiuqin Wu [X] (Inactive) added a comment - 25/Jul/18 12:56 PM DM-15176 has been created to address the issues raised by reviewer.