# Luxon date bug / issue

**URL:** <https://community.glideapps.com/t/luxon-date-bug-issue/59703>\
**Category:** Ask for Help\
**Created:** [March 26, 2023, 12:50pm UTC](https://community.glideapps.com/t/luxon-date-bug-issue/59703 "2023-03-26T12:50:13Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![abdo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/abdo/32/36540_2.png) [@abdo](https://community.glideapps.com/u/abdo)\
**Post date:** [March 26, 2023, 12:50pm UTC](https://community.glideapps.com/t/luxon-date-bug-issue/59703/1 "2023-03-26T12:50:13Z")

</div>

I’m placing today luxon formatted date value in a date column. Then when relating that column to rows one user get rows with a tomorrow date falling “within” today date ! Other users didn’t get this.

I’ve heard that Luxon causes some issues, could this be one? How can Mar 27 be within a Mar 26 luxon date?

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [March 26, 2023, 2:45pm UTC](https://community.glideapps.com/t/luxon-date-bug-issue/59703/2 "2023-03-26T14:45:12Z")

</div>

Where are you storing your data? Do you have an option to make the date column “respect time zones”?

---

<div class="post-metadata">

**Author:** ![abdo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/abdo/32/36540_2.png) [@abdo](https://community.glideapps.com/u/abdo)\
**Post date:** [March 26, 2023, 4:57pm UTC](https://community.glideapps.com/t/luxon-date-bug-issue/59703/3 "2023-03-26T16:57:09Z")

</div>

Yes i do have that option  
I’m storing the date as a user specific column in the user profile sheet.

its really a search date. User selects a date and views orders on that date.  
For one particular user they are viewing orders on that date and the next day.

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [March 27, 2023, 12:06am UTC](https://community.glideapps.com/t/luxon-date-bug-issue/59703/4 "2023-03-27T00:06:04Z")

</div>

I would advise using a math column to convert the date to a numerical value.

YEAR(D) \* 10000 + MONTH(D) \* 100 + DAY(D)

With D being the date would give you something like 20230307.

Then you can use that value to filter/make a relation etc, I think it’s much more safer than Luxon, which can act weird in some devices.

---

<div class="post-metadata">

**Author:** ![abdo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/abdo/32/36540_2.png) [@abdo](https://community.glideapps.com/u/abdo)\
**Post date:** [March 27, 2023, 8:59am UTC](https://community.glideapps.com/t/luxon-date-bug-issue/59703/5 "2023-03-27T08:59:34Z")

</div>

To be honest Luxon has been fine with us up until yesterday. I just realized the UK changed time zone yesterday… the user experiencing the issue was from London. I guess its change in time zone related

Will look into using math rather than Luxon.