---
title: "Discussion on \"The agent renamed the field in code and never told the database, so old rows read as undefined\" | Hashnode"
description: "Discussion on \"The agent renamed the field in code and never told the database, so old rows read as undefined\". The agent renamed displayName to fullName across types and components; fresh-fixture tests stay green, but old rows still carry the old key, so a read returns undefined. A rename is a refactor only when every sink keeps the same shape; persisted rows, caches, and queues remember the old field."
url: "https://hashnode.com/posts/agent-renames-persisted-field-without-migration/6add14baee63705a76ce5cb9"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [The agent renamed the field in code and never told the database, so old rows read as undefined](https://blogs.powerduck.com/agent-renames-persisted-field-without-migration?utm_source=hashnode&utm_medium=feed)

The agent renamed displayName to fullName across types and components; fresh-fixture tests stay green, but old rows still carry the old key, so a read returns undefined. A rename is a refactor only when every sink keeps the same shape; persisted rows, caches, and queues remember the old field.

Oct 24 · 4 min read · blogs.powerduck.com  
Read the article

-   [#aiagents](https://hashnode.com/tag/aiagents)
-   [#migration](https://hashnode.com/tag/migration)
-   [#types](https://hashnode.com/tag/types)
-   [#contract](https://hashnode.com/tag/contract)

## Written by

[Powerduck](https://hashnode.com/@powerduck)

@powerduck · hon

  
[View profile](https://hashnode.com/@powerduck)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
