@Jean_Pierre_Traets I think that’s a good solution given Coda’s current capabilities, but I also think it would be great if Coda added support for @Ashish_Bogawat1’s schema.
Ashish’s schema makes sense because official holidays are quite a different type of record than individual employees’ time booked off. For example employee leaves would apply only to one particular employee, and might have other requirements like manager’s approval, etc. You could include official holidays in this employee leave table and just leave a bunch of columns blank for them, but I think it could lead to a lot of filtering & formula overhead in other areas of the doc.
Of course, because calendars are just another table view, it would put a lot of strain on Coda’s data model to accommodate something like having a calendar display multiple tables. Perhaps the solution is to recognize that calendar views are a special kind of thing (not just another table view) and allow the display of multiple tables within the same calendar (each with their own config parameters e.g. which column is the start date etc).