Timeline for Office Hours in PostgreSQL
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 4, 2021 at 21:54 | history | edited | Andriy M | CC BY-SA 4.0 |
added a space to fix formatting
|
| May 4, 2021 at 11:19 | history | edited | Vérace | CC BY-SA 4.0 |
added 36 characters in body
|
| May 4, 2021 at 11:14 | comment | added | Vérace |
You will have to make bank_holiday editable for variable holidays - Easter for example. Here in Ireland, we normally have the "May Day" holiday on the following Monday - i.e. also variable). You could have the t table (should maybe have called it calendar or days_of_year?) on disk - even 25 years of data wouldn't be very much. If you found my answer helpful and/or correct, please mark it as such - not so much for points - I have plenty of those now - but upvoted answers tend to be found by searches. I upvoted yours, not looking for a quid pro quo, but 'cos I learnt stuff from it! :-)
|
|
| May 4, 2021 at 10:46 | comment | added | guettli | Thank you very much for your answer. I will take your idea that there are tables which contain the source data (which can be edited by users via a GUI), and there is a table which contains the generated entries. I will add a column "source" to the table holding the generated data, so that I update/delete these entries if the source data gets changed. | |
| May 4, 2021 at 7:52 | history | edited | Vérace | CC BY-SA 4.0 |
Do the whole thing in one pass!
|
| May 3, 2021 at 21:40 | history | answered | Vérace | CC BY-SA 4.0 |