Closed lbradley-mm closed 9 months ago
Thanks for opening the issue, @lbradley-mm.
What would you see as the outcome here, would it be added to some README or other documentation, or you think it should be somehow part of the code, or something else?
For exports that time out, the standard approach that I would recommend is using a queued job that runs a build task which will either email the exported CSV (as there's no time limit for queued jobs), or store it in the file system/assets section somewhere for future access etc.
Writing a db procedure might be a cool trick, but it circumvents all the CMS/ORM level checks, data transformations, extensions etc etc, so it's not really a full-featured replacement. Also different db backends may treat the SQL code differently and it may not be compatible with different db engines.
With that, I will close the issue for now as I don't see an easy way how this can be used or integrated by the module itself. Please do feel free to leave further comments or e.g. a link to a gist with the procedure so that people can use it for inspiration should they come across the same need.
Thank you for your understanding and time creating the issue 👍!
Hi @michalkleiner I'd say you're right that it's probably just a useful tool for exports that may go into documentation or similar The idea of queuing and emailing an export would probably be the best solution for the scenario I currently have Thanks
I made a start on this as Full CSV exports can time out if there are a LOT of submissions