29 lines
1.2 KiB
Markdown
29 lines
1.2 KiB
Markdown
 
|
# Is there advantage of using Integer in table column created_at? (SitePoint forum)
|
||
|
|
|
||
|
|
## Metadata
|
||
|
|
|
||
|
|
| Field | Value |
|
||
|
|
|---|---|
|
||
|
|
| Institute | Molodetz Institute — Research & Retrieval Division |
|
||
|
|
| Subject | agent-memory-recency-tracking |
|
||
|
|
| Document type | Source Citation Card |
|
||
|
|
| Tier | 2 |
|
||
|
|
| Source title | Is there advantage of using Integer in table column created_at? |
|
||
|
|
| Source URL | https://www.sitepoint.com/community/t/is-there-advantage-of-using-integer-in-table-column-created-at/343308 |
|
||
|
|
| Source type | forum thread |
|
||
|
|
| Date researched | 2026-10-09 |
|
||
|
|
| Researched by | tai (agent), model: Claude Sonnet 5, on behalf of retoor |
|
||
|
|
| Research method | Search aggregator result listing (not independently opened or quoted) |
|
||
|
|
| Confidence | Not independently verified |
|
||
|
|
| Status | Active |
|
||
|
|
|
||
|
|
## Why it's here
|
||
|
|
|
||
|
|
Surfaced by the search "SQLite last_accessed column unix timestamp vs datetime performance indexing" as a directly on-topic forum thread (integer vs. other types for a timestamp column); not opened or quoted independently during this pass beyond what's already captured in the Tier 1 dossier for the primary SQLite forum source.
|
||
|
|
|
||
|
|
## Changelog
|
||
|
|
|
||
|
|
| Date | Change |
|
||
|
|
|---|---|
|
||
|
|
| 2026-10-09 | Logged as consulted-but-not-analyzed. |
|