bacon_pdp

One database service but separate databases running inside of the service. Each database has 3 accounts: table_owner (no remote access), proc_owner (only table specific permissions and the owner of all stored procedures; no remote access) and application_account (no table access and only execute permissions on the proc_owner’s stored procedures).

Which means that even if the application is compromised, it can not compromise the database. It can only use approved stored procedures that check their inputs and abort on the smallest deviation from expected inputs.

Second the link must be provided

This is literally ripping a hole in the anti-submarine network that is essential to national defense…

Thank you for the recommendation.

There is no such thing as no code, just code that someone else wrote. Not that such code isn’t trivial to get from a basic LLM that you can run locally for pennies a year.

blog.mlc.ai/…/GPU-Accelerated-LLM-on-Orange-Pi

Just setup a standard PostgreSQL database and then work with the LLM to write some C# code to connect to it and create, update and delete data per your own system needs. Hire a part time programmer if you need more help. They usually can get you where you want to be cheaply if they are FSF developers and you don’t restrict them from using the code they write for you.

Yeah, no they plan on going full identity validation