reports: finalize database connection isolation

[dustymc]

Need Help?

If you require assistance rewriting reports, just ask.

Source

#96

Summary

#96 introduces isolated SQL and detects inappropriate database connections, but does not prevent executing reports with them. The new structure cannot prevent ArctosDB/arctos#8342 until this is completed, but the desire is to be as non-disruptive as possible so a stage two is necessary.

• DLM will begin rewriting and optimizing reports, @mkoo will orchestrate. Note that reports: isolate database connection #96 does protect report_sql; a report that uses report_sql can only be edited with write_sql permissions.
• adjust timeout in the reporter (currently 30s) to safe-and-reasonable while rewriting
• continue developing documentation while rewriting (https://handbook.arctosdb.org/documentation/reports.html#write_sql)
• Finalize; implement this issue

User Interface Changes

The red warning of next release will become a hard stop when this is implemented.

Data Structure Changes

none

[amgunderson]

I just got my labels working, what does this mean?

[dustymc]

See #96 for background, this filter is necessary to protect the system.

If you're happy with a report, you can just let me know how to find it and I can upgrade. Nothing will change, I'll just check that the SQL isn't doing anything crazy and move it to a protected place.

Anyone is of course welcome to the new role as well, it basically boils down to agreeing to develop in test and not bringing anything to production until it's been tested.

https://handbook.arctosdb.org/documentation/reports.html will continue to develop as we work through this.

[mkoo]

As has been stated in other issues and meetings, a word of reassurance-- there will be no changes to your reports-- we are moving SQL to more secure fields and in this transition you may see red boxes, skulls, green checks, etc as these measures are completed. We dont want your reports to change either! There's no action on your part needed and you can continue to print as needed. But since Dusty is also doing QA/QC on SQL this is a multistep process.

As usual, please file an issue if you want a new report!

[dustymc]

Tech chat with @mkoo - will contact heavy users, check back re: blocking unfiltered execution 20250201.

To get rid of the scary icon in the reporter, just let me know how to find your needed reports in whatever way works best for you.

[Kmullineaux]

@dustymc Are we able to edit the tags once they've been changed to the new SQL, or should we ensure the tags are finished before requesting help? thanks!

[dustymc]

@Kmullineaux https://arctos.database.museum/Admin/user_roles.cfm#write_report can alter anything but SQL, https://arctos.database.museum/Admin/user_roles.cfm#write_sql can alter SQL. The recommendation will always be to start by gathering the data then working on layout no matter what the current environment look like or who's involved. I'm happy to help with SQL anywhere along the way and can optimize around requested data rather than current usage, just let me know how I can help.

[Kmullineaux]

@dustymc I've created a new issue for NHSM reports so I'm not filling up this one!