...
- We'd like to keep getting metadata with the result set from dbserv to be able to interpret the result set without an extra call needed. (Yes from DAX)
- Currently flag fields (bit type in db) is passed to us as string fields, ex. "b'\x00'". All int fields are passed as long. In general, I am concerned about custom python code, which converts mySQL types. (`https://github.com/lsst/dax_dbserv/blob/master/python/lsst/dax/dbserv/compat/fields.py`) (may have been fixed)
- MySQL gives a hint of the display width of the field. Can we carry it over? (No for now)
- When the result set is empty, we should still get the metadata. (Yes from DAX)