improvement(tables): rename TTL column to Expiration

Author: j15z

apps/docs/content/docs/en/tables/index.mdx

@@ -24,15 +24,15 @@ Every column has a type, which decides how its values are stored and validated.
 | **Currency** | An amount in a currency you pick per column | `$1,234.56` |
 | **Boolean** | `true` or `false` | `true` |
 | **Date** | A date | `2026-03-16` |
-| **TTL** | An absolute row expiration time, stored as Unix epoch seconds (seconds since January 1, 1970 UTC) | `1773671400` |
+| **Expiration** | An absolute row expiration time, stored as Unix epoch seconds (seconds since January 1, 1970 UTC) | `1773671400` |
 | **JSON** | An object or array | `{ "tier": "pro" }` |
 | **Select** | One of a fixed set of options, or several | `Pro` |
 
 Types are enforced as you enter values, so a Number column only takes numbers.
 
 A Currency column stores a plain number and renders it in the currency you choose for that column, so filters, sorts, and exports all see the amount itself. Changing a column's currency relabels it — it does not convert the amounts.
 
-A table can have one TTL column. Adding it enables row expiration; rows with a non-empty TTL value become eligible for deletion after that time passes. Cleanup runs periodically, so actual row removal may happen after the TTL timestamp rather than exactly at it. Deleting the TTL column disables expiration for the table. TTL cells use the date editor, while APIs and workflows read and write integer Unix epoch seconds.
+A table can have one Expiration column. Adding it enables row expiration; rows with a non-empty expiration value become eligible for deletion after that time passes. Cleanup runs periodically, so actual row removal may happen after the expiration timestamp rather than exactly at it. Deleting the Expiration column disables expiration for the table. Expiration cells use the date editor, while APIs and workflows read and write integer Unix epoch seconds.
 
 ## Editing a table
 

apps/sim/app/workspace/[workspaceId]/tables/[tableId]/components/column-config-sidebar/column-types.test.ts

@@ -17,7 +17,7 @@ describe('columnTypeOptionsForTable', () => {
     )
 
     expect(availableTtl?.disabledReason).toBeUndefined()
-    expect(unavailableTtl?.disabledReason).toBe('Only one TTL column allowed per table')
+    expect(unavailableTtl?.disabledReason).toBe('Only one Expiration column allowed per table')
   })
 
   it('keeps TTL enabled while editing the existing TTL column', () => {

apps/sim/lib/table/__tests__/validation.test.ts

@@ -204,7 +204,7 @@ describe('Validation', () => {
       } as TableSchema)
 
       expect(result.valid).toBe(false)
-      expect(result.errors).toContain('A table can have at most 1 TTL column')
+      expect(result.errors).toContain('A table can have at most 1 Expiration column')
     })
 
     it('should reject null schema', () => {

apps/sim/lib/table/column-types/ttl.ts

@@ -64,7 +64,7 @@ function epochSecondsToEditable(value: unknown, timeZone?: string): string | nul
 
 export const ttlColumnType: ColumnTypeDefinition = {
   id: 'ttl',
-  label: 'TTL',
+  label: 'Expiration',
   maxPerTable: 1,
   icon: TypeTtl,
   jsonbCast: 'numeric',

apps/sim/lib/table/columns/ttl-limit.test.ts

@@ -62,13 +62,13 @@ describe('TTL column mutation limit', () => {
   it('rejects adding a second TTL column before persistence', async () => {
     await expect(
       addTableColumn('table-1', { name: 'another_expiry', type: 'ttl' }, 'request-1')
-    ).rejects.toThrow('A table can have at most 1 TTL column')
+    ).rejects.toThrow('A table can have at most 1 Expiration column')
   })
 
   it('rejects retyping another column to TTL before scanning cells', async () => {
     await expect(
       updateColumnType({ tableId: 'table-1', columnName: 'name', newType: 'ttl' }, 'request-1')
-    ).rejects.toThrow('A table can have at most 1 TTL column')
+    ).rejects.toThrow('A table can have at most 1 Expiration column')
     expect(mockTimeoutExecute).toHaveBeenCalled()
   })
 })