When a col-type is (or :null :timestamp) then dao-table-column-inflate fails with nulls [fixed]

[vindarel]

I added a column in my model with a nullable timestamp:

   (read-date
    :accessor read-date
    :initarg :read-date
    :initform nil
    :type (or null number)
    :col-type (or :null :timestamp)
    :documentation "The day we finished this book.")

when requesting objects, I now get

Failed to parse "" as an rfc3339 time: NIL

  0: ((LABELS PARSE-ERROR :IN LOCAL-TIME::%SPLIT-TIMESTRING) #<unavailable argument>)
  1: (LOCAL-TIME::%SPLIT-TIMESTRING #<unavailable argument> :START #<unavailable argument> :END #<unavailable argument> :FAIL-ON-ERROR #<unavailable argument> :TIME-SEPARATOR #<unavailable argument> :DATE-..
  2: (LOCAL-TIME:PARSE-TIMESTRING "" :START NIL :END NIL :FAIL-ON-ERROR T :TIME-SEPARATOR #\: :DATE-SEPARATOR #\- :DATE-TIME-SEPARATOR #\  :FRACT-TIME-SEPARATORS (#\. #\,) :ALLOW-MISSING-ELEMENTS T :ALLOW-..
  3: ((:METHOD MITO.DAO.MIXIN:MAKE-DAO-INSTANCE (MITO.CLASS.TABLE:TABLE-CLASS)) …

• should I make the default a dummy date, and how?
• maybe Mito can avoid inflate this value

WDYallT? thanks

[fukamachi]

Thanks. It seems like a bug. I'm going to fix it.

[vindarel]

Thank you 🙏 (it's merged and working)