# Runtime Schedule **URL:** \ **Category:** Ignition\ **Created:** [May 18, 2022, 7:26pm UTC](https://forum.inductiveautomation.com/t/runtime-schedule/59745 "2022-05-18T19:26:23Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [May 18, 2022, 7:29pm UTC](https://forum.inductiveautomation.com/t/runtime-schedule/59745/2 "2022-05-18T19:29:17Z")
Have you seen this discussion: > [@Script for periodically changing shift time](https://forum.inductiveautomation.com/t/script-for-periodically-changing-shift-time/51058/3): > > Hi Berkay, I like to solve this kind of problem with a smart database, like PostgreSQL, where I can define a pattern and repeat it with table generating functions. I tweaked one of my implementations to serve as an example: create table shift\_schedules (shift\_id serial, shift\_name varchar(255), refdate date, repeat int, tzname varchar(255), primary key (shift\_id)); insert into shift\_schedules (shift\_name, refdate, repeat, tzname) values ('Berkay Cinar 3wk', '2021-07-26', 21, 'America/Ne… Let them use shift definitions. No UI for it at the moment, but I think you can handle it. 😁 --- _[View the full topic](https://forum.inductiveautomation.com/t/runtime-schedule/59745)._