You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
A source fill that spans a table re-declaration stamps created time under the old schema #3616
A source fill (getFromSource() in resources/Table.ts) decides whether to stamp the created-time field before it awaits the model hooks, and commits with that decision. If the table is re-declared during that await:
a newly added created-time field is left unstamped on the filled record, and later updates do not fill it;
a removed created-time field is still stamped, under its old name.
Possible fix: record at decision time only whether the source supplied a created time, and resolve the attribute from the live createdTimeProperty inside the commit callback. Needs a test with a gated @embed/@decide hook on a sourced table to hold the fill across a re-declaration.
Related: the same fill reads updatedTimeProperty live at commit, so a fill spanning a reload can stamp created and updated time under different schemas. Any fix here should decide both timestamps the same way.
Activity
kriszyp commentedon Oct 27, 2026
Related: the same fill reads
updatedTimePropertylive at commit, so a fill spanning a reload can stamp created and updated time under different schemas. Any fix here should decide both timestamps the same way.— Claude Opus 5.5