** Parse non-RFC3339 added_at values in list rows**
row_to_book now calls Book::from_row, which loads added_at as Option<DateTime<Utc>>. In rusqlite, that conversion expects RFC3339 or unix timestamps, but this codebase writes added_at via SQLite CURRENT_TIMESTAMP (YYYY-MM-DD HH:MM:SS), so listing can now fail with a row conversion error instead of rendering results. The previous mapper explicitly parsed SQLite timestamp formats and degraded to None, so this introduces a regression for databases containing default timestamp strings.
Useful? React with 👍 / 👎.
Originally posted by @chatgpt-codex-connector[bot] in #20 (comment)
** Parse non-RFC3339
added_atvalues in list rows**row_to_booknow callsBook::from_row, which loadsadded_atasOption<DateTime<Utc>>. In rusqlite, that conversion expects RFC3339 or unix timestamps, but this codebase writesadded_atvia SQLiteCURRENT_TIMESTAMP(YYYY-MM-DD HH:MM:SS), so listing can now fail with a row conversion error instead of rendering results. The previous mapper explicitly parsed SQLite timestamp formats and degraded toNone, so this introduces a regression for databases containing default timestamp strings.Useful? React with 👍 / 👎.
Originally posted by @chatgpt-codex-connector[bot] in #20 (comment)