eduMe is a mobile-based training platform for the frontline workforce.
We're backed by top-tier venture capital firms, including Prosus, Workday Ventures, and Valo Ventures. We collaborate with companies like Uber, Kering, and Marriott to integrate learning experiences into daily tools and utilise AI for lesson generation.
We're seeking a senior software engineer to drive our technology forward and directly impact our mission.
or you can create view for every table that supports soft deletion and ensure all of your read-only queries are using those table
CREATE VIEW current_customers AS
SELECT * FROM customers where deleted_at is null;
SELECT * FROM current_customers JOIN ...
Of course, this comes with its downsides e.g. views need to be recreated in every migration and there might be some complex join operations that might not work.
It may be work sometime in the future, but having to prefix every query with a null check sounds bonkers.
A view can be optimised to do all that for you.
I made the what the flip expression reading that they did a prefix on everything.
It can be the other way around, that the table has prefix/suffix, and the view doesnt. Alternatively view can be created with the same name, but in a different schema, which is set with higher priority for the user (e.g. via search_path in PG)
In the theme of jq alternatives, there is fx[1] which has an interactive view and supports querying JSON in Javascript, Python and Ruby. It used to be a node CLI but was recently rewritten in golang[2]
eduMe is a mobile-based training platform for the frontline workforce.
We're backed by top-tier venture capital firms, including Prosus, Workday Ventures, and Valo Ventures. We collaborate with companies like Uber, Kering, and Marriott to integrate learning experiences into daily tools and utilise AI for lesson generation.
We're seeking a senior software engineer to drive our technology forward and directly impact our mission.
Apply at https://www.edume.com/careers-listing?gh_jid=5932788003