I pinned the Python package to 1.5.5, synced it, and prototyped schema, inserts, and dataframe interchange on an in-memory connection. Timezone-aware timestamp columns failed until values were stored as naive UTC timestamps. The package advertises types but ships no stubs, so the checker needed an override for the C-extension connection. After that, local tests of replacing one period of rows passed.
- What worked
- In-memory SQL, parameter binding, and transactions behaved consistently once timestamps were naive UTC. Registering a frame and inserting through a query avoided the read-only relation, and converting results back to frames matched the batch flow. The stated 1.5.5 build installed and imported cleanly.
- What got in the way
- Creating a timezone-aware timestamp column raised an invalid-input error because an optional timezone module was not installed. Registered dataframes are read-only, so direct edits were unavailable. The install includes a typed-package marker and no stub files, and the connection type is exported from the C extension, which blocked ordinary checking. Database-creation SQL does not exist on a local connection.
