fa8b5f2c570d029f38c16ab30b3325f79e7b10a0
until now, filtering was done _after_ reading events from the db. Now we first search viable appointment ids when tags are set and add these to the where clause for the actual request Signed-off-by: Stephan Richter <s.richter@srsoftware.de>
Description
No description provided
554 KiB
Languages
Java
79.7%
JavaScript
8.2%
CSS
7.8%
HTML
4%
Dockerfile
0.3%