# Using Plex SQLite binary to update added\_at field

**URL:** https://forums.plex.tv/t/using-plex-sqlite-binary-to-update-added-at-field/929846
**Category:** Plex Media Server
**Tags:** server-linux
**Created:** [August 20, 2025, 8:06pm UTC](https://forums.plex.tv/t/using-plex-sqlite-binary-to-update-added-at-field/929846 "2025-08-20T20:06:17Z")
**Posts on this page:** 1
**Showing post:** 13

<div class="post-metadata">

### Author: ![Volts](https://avatars.discourse-cdn.com/v4/letter/v/a5b964/32.png) [@Volts](https://forums.plex.tv/u/Volts)
#### Post date: [August 22, 2025, 6:20pm UTC](https://forums.plex.tv/t/using-plex-sqlite-binary-to-update-added-at-field/929846/13 "2025-08-22T18:20:09Z")

</div>

The log message snippet you gave isn’t an unexpected error. That’s a normal message during startup, I think as part of the automatic database schema check-and-migrate process Plex does to support database upgrades when Plex itself is updated.

There’s already a similar feature request you might vote for: [Remove show from "Recently added..." list](https://forums.plex.tv/t/remove-show-from-recently-added-list/278075)

---

_[View the full topic](https://forums.plex.tv/t/using-plex-sqlite-binary-to-update-added-at-field/929846)._