2 ms·
I’m confused. I understood this to generate static pages. If you never update them, the report wouldn’t change right? E.g. it executes the queries during build
by Aeolun 5y ago
I’m confused. I understood this to generate static pages. If you never update them, the report wouldn’t change right?
E.g. it executes the queries during build time, not on every load.
- amcaskill 5y agoYou are correct that Evidence executes queries at build time, not at load time. In a production environment for business reporting we would expect users to be building their project a few times a day, if not more often. For example, we compile all of our KPIs for evidence into an evidence project, and we trigger a build of that project twice a day so that it has up-to-date metrics for us. Your question is making me think about what an incremental build strategy could/should look like, but that’s a bit down the road for us.
- Aeolun 5y agoProbably not worth it to do incremental I think. At least, unless your reporting queries take ages (now that I say that, I can practically guarantee that someone is going to think it’s normal to have a report run for several days) Either way, my point was that if the final output is a few static HTML files, it’s probably not too much of a problem to save literally every iteration of a report.