It's surely not one of my routine tasks but lately I had to modify some values in a database, and by lack of an application-specific GUI to do so, I chose DBISQL to display the according rows and modified them in the result tab. (I should add I'm still more the dbisqlc type of guy, as John will know.)
In general, this is a nice feature, and the according DML statements get even caught in DBISQL's history tab. And modifying strings, numbers and date values works well.
However, when editing timestamp values, it seems a bit harder. I'm using the defaults for date_order, date_format and the like:
There are two things that seem sub-optimal:
Whereas its common pracise to fill a timestamp via SQL by just setting the DATE part, the editor seems only to accept timestamp values when I enter at least the hour and minute part, too. If I leave them out (as I often just want to set the date), the value is silently discarded, and a NULL value is stored. - If something is missing, I would really appreciate a conversion error message or the like - though I would suggest to accept the omitted time as the default "00:00:00.000000".
When entering the "edit mode", the timestamp values is displayed differently, namely in a "long format" with different date order and a leading month name - that's at least quite irritating:
Am I doing something wrong here, or might this behaviour be optimized?
28 Mar '12, 06:05