# "Originally Available" ... unavailable **URL:** \ **Category:** Metadata & Adding Files\ **Tags:** server-linux, other-dev\ **Created:** [April 27, 2022, 8:17pm UTC](https://forums.plex.tv/t/originally-available-unavailable/790403 "2022-04-27T20:17:01Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![cn\_x](https://avatars.discourse-cdn.com/v4/letter/c/ed655f/32.png) [@cn\_x](https://forums.plex.tv/u/cn_x)\ **Post date:** [April 27, 2022, 8:17pm UTC](https://forums.plex.tv/t/originally-available-unavailable/790403/1 "2022-04-27T20:17:01Z")
If it’s not broken, why fix it? If you change something, why not test it first before giving your users something broken? ![fixing_problems](https://global.discourse-cdn.com/plex/original/4X/5/5/7/557112807363ef79daa1cc1d6aa1337cee19ad5d.png) Server Version#: 1.26.0.5715 (Edit: I didn’t even bugcheck my own thread post, apparently. Changed server version from 1.26.0.5725 to 1.26.0.5715) ---
**Author:** ![Volts](https://avatars.discourse-cdn.com/v4/letter/v/a5b964/32.png) [@Volts](https://forums.plex.tv/u/Volts)\ **Post date:** [April 27, 2022, 8:22pm UTC](https://forums.plex.tv/t/originally-available-unavailable/790403/2 "2022-04-27T20:22:08Z")
What issue are you having? Your message isn’t clear. The issues I’m aware of with Originally Available At and Year appear to be resolved in **1.26.1.5772**. ---
**Author:** ![Tony\_T](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/tony_t/32/311528_2.png) [@Tony\_T](https://forums.plex.tv/u/Tony_T)\ **Post date:** [April 27, 2022, 8:23pm UTC](https://forums.plex.tv/t/originally-available-unavailable/790403/3 "2022-04-27T20:23:20Z")
1.26.1.5772. Is still beta, right? ![image](https://global.discourse-cdn.com/plex/original/4X/d/0/b/d0b1c39cd475aa27e4f073615cde988a9e112fa1.jpeg) ---
**Author:** ![Volts](https://avatars.discourse-cdn.com/v4/letter/v/a5b964/32.png) [@Volts](https://forums.plex.tv/u/Volts)\ **Post date:** [April 27, 2022, 8:29pm UTC](https://forums.plex.tv/t/originally-available-unavailable/790403/4 "2022-04-27T20:29:00Z")
Yes. I think a lot of people routinely use betas that shouldn’t, because they are then crabby when there are bugs. But 1.26.0 was public and had these issues. Bugs happen in public releases too. Such is life. So if you’re using 1.26.0 right now, and are having issues with Originally Available At and Year, and don’t feel like waiting … 1.26.1.5762 is a relatively small update, and appears to resolve those specific issues. ---
**Author:** ![Tony\_T](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/tony_t/32/311528_2.png) [@Tony\_T](https://forums.plex.tv/u/Tony_T)\ **Post date:** [April 27, 2022, 8:30pm UTC](https://forums.plex.tv/t/originally-available-unavailable/790403/5 "2022-04-27T20:30:15Z")
Dates are just cosmetic, so I’ll wait for the public release. ---
**Author:** ![Volts](https://avatars.discourse-cdn.com/v4/letter/v/a5b964/32.png) [@Volts](https://forums.plex.tv/u/Volts)\ **Post date:** [April 27, 2022, 8:32pm UTC](https://forums.plex.tv/t/originally-available-unavailable/790403/6 "2022-04-27T20:32:53Z")
Hah, that’s what I said too - that it’s entirely cosmetic! Turns out this can also affect people using Smart Playlists or filtering by Year. I agree; if you aren’t impacted … ---
**Author:** ![anon5074910](https://avatars.discourse-cdn.com/v4/letter/a/db5fbb/32.png) [@anon5074910](https://forums.plex.tv/u/anon5074910)\ **Post date:** [April 27, 2022, 8:33pm UTC](https://forums.plex.tv/t/originally-available-unavailable/790403/7 "2022-04-27T20:33:27Z")
Do you happen to know why plex are messing about with the date formats within the db schema? I come from a software background and the changes they are making do not make sense to me. Appears to be change for changes sake! It also seems haphazard as only some tables have changed. ---
**Author:** ![cn\_x](https://avatars.discourse-cdn.com/v4/letter/c/ed655f/32.png) [@cn\_x](https://forums.plex.tv/u/cn_x)\ **Post date:** [April 27, 2022, 8:35pm UTC](https://forums.plex.tv/t/originally-available-unavailable/790403/8 "2022-04-27T20:35:03Z")
I guess this is the real question I was getting at in a crabby way. ---
**Author:** ![Tony\_T](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/tony_t/32/311528_2.png) [@Tony\_T](https://forums.plex.tv/u/Tony_T)\ **Post date:** [April 27, 2022, 8:37pm UTC](https://forums.plex.tv/t/originally-available-unavailable/790403/9 "2022-04-27T20:37:13Z")
Are the tables changing? I thought it was just a UI error when converting the UTC date (in the database) to local time. ---
**Author:** ![anon5074910](https://avatars.discourse-cdn.com/v4/letter/a/db5fbb/32.png) [@anon5074910](https://forums.plex.tv/u/anon5074910)\ **Post date:** [April 27, 2022, 8:38pm UTC](https://forums.plex.tv/t/originally-available-unavailable/790403/10 "2022-04-27T20:38:08Z")
The format of the dates in the db have changed for some tables but not all. ---
**Author:** ![Volts](https://avatars.discourse-cdn.com/v4/letter/v/a5b964/32.png) [@Volts](https://forums.plex.tv/u/Volts)\ **Post date:** [April 27, 2022, 8:39pm UTC](https://forums.plex.tv/t/originally-available-unavailable/790403/11 "2022-04-27T20:39:50Z")
> [@Tony\_T](#): > > Are the tables changing? Datetime fields in some tables, including `metadata_items`, have been changed from a text format `YYYY-MM-DD HH:MM:SS` to a unix-style epoch seconds format. ---
**Author:** ![Tony\_T](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/tony_t/32/311528_2.png) [@Tony\_T](https://forums.plex.tv/u/Tony_T)\ **Post date:** [April 27, 2022, 8:39pm UTC](https://forums.plex.tv/t/originally-available-unavailable/790403/12 "2022-04-27T20:39:59Z")
Thanks. How is that fixed (when I update). Do I need to do a metadata refresh? ---
**Author:** ![Volts](https://avatars.discourse-cdn.com/v4/letter/v/a5b964/32.png) [@Volts](https://forums.plex.tv/u/Volts)\ **Post date:** [April 27, 2022, 8:41pm UTC](https://forums.plex.tv/t/originally-available-unavailable/790403/13 "2022-04-27T20:41:40Z")
When you update, Plex will perform a database migration automatically, converting the values in those fields to the new format. These bugs were in the UI and PMS internal APIs - PMS wasn’t consistently updated to use the new date format! ---
**Author:** ![SwiftPanda16](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/swiftpanda16/32/81839_2.png) [@SwiftPanda16](https://forums.plex.tv/u/SwiftPanda16)\ **Post date:** [April 27, 2022, 8:43pm UTC](https://forums.plex.tv/t/originally-available-unavailable/790403/14 "2022-04-27T20:43:35Z")
The objectively correct way to store date / time. ---
**Author:** ![anon5074910](https://avatars.discourse-cdn.com/v4/letter/a/db5fbb/32.png) [@anon5074910](https://forums.plex.tv/u/anon5074910)\ **Post date:** [April 27, 2022, 8:44pm UTC](https://forums.plex.tv/t/originally-available-unavailable/790403/15 "2022-04-27T20:44:46Z")
Still comes down to why? Only reason I can’t think of is that it makes it (slightly) more complicated to see the human readable dates when reviewing the db directly. Could be part of the integration they are working on with other streaming services. ---
**Author:** ![Volts](https://avatars.discourse-cdn.com/v4/letter/v/a5b964/32.png) [@Volts](https://forums.plex.tv/u/Volts)\ **Post date:** [April 27, 2022, 8:47pm UTC](https://forums.plex.tv/t/originally-available-unavailable/790403/16 "2022-04-27T20:47:33Z")
Textual dates are gross, but at least it was a sane ISO8601 subset format before. Any bets about **2038-01-19 03:14:08**? ---
**Author:** ![Volts](https://avatars.discourse-cdn.com/v4/letter/v/a5b964/32.png) [@Volts](https://forums.plex.tv/u/Volts)\ **Post date:** [April 27, 2022, 8:49pm UTC](https://forums.plex.tv/t/originally-available-unavailable/790403/17 "2022-04-27T20:49:54Z")
The database isn’t intended to be a human-consumable interface. This doesn’t bother me at all. Internally they were probably converting the date-text to an epoch-style string every time they did a comparison, and then back again for storage. Makes more sense for the computer to store computer-things in a computer-readable format. ---
**Author:** ![anon5074910](https://avatars.discourse-cdn.com/v4/letter/a/db5fbb/32.png) [@anon5074910](https://forums.plex.tv/u/anon5074910)\ **Post date:** [April 27, 2022, 8:52pm UTC](https://forums.plex.tv/t/originally-available-unavailable/790403/18 "2022-04-27T20:52:08Z")
Sure but seems like a lot of development effort just to rework internal date formats. Many other things would seem more important but sure what do I know… 😜 ---
**Author:** ![7venflix](https://avatars.discourse-cdn.com/v4/letter/7/7ea924/32.png) [@7venflix](https://forums.plex.tv/u/7venflix)\ **Post date:** [April 27, 2022, 8:56pm UTC](https://forums.plex.tv/t/originally-available-unavailable/790403/19 "2022-04-27T20:56:30Z")
2 weeks ago I came on the forums to tell complain about this. I am so glad other people are seeing what I did. ---
**Author:** ![Volts](https://avatars.discourse-cdn.com/v4/letter/v/a5b964/32.png) [@Volts](https://forums.plex.tv/u/Volts)\ **Post date:** [April 27, 2022, 8:57pm UTC](https://forums.plex.tv/t/originally-available-unavailable/790403/20 "2022-04-27T20:57:41Z")
> [@anon5074910](#): > > Many others things would seem more important I wasn’t there, but I’ll bet $2 it went like this: "I’m working on feature X (or bug Y) which uses dates. This is twice as hard as it should be, because we’re using these dumb text dates in the database. I could also use the dumb text dates in the new feature, but that would just be perpetuating the problem. If I refactor this code to use sane dates, that will help me get my work done faster - and remove some technical debt in the process. And I’ll feel more job satisfaction because I’ve improved the code a bit, instead of just kicking the can down the road." I’ll bet another $1 that they’re really annoyed that they introduced bugs that made it into public view. [Next page](https://forums.plex.tv/t/originally-available-unavailable/790403.md?page=2)