wouldn't you be able to do the same even with FK in place?
what FK would prevent you from doing would be deleting a user before all his relationships are removed. That should prevent you to ending up with inconsistent data inside the tables.
In my experience with regular Postgres databases shared across many teams, inconsistent/broken references is seen as a much less risky thing to do than, say, cascading a delete. Usually a broken reference is of no consequence. And you don’t use FKs, people tend to bake that into how they code things without much trouble.
I've oft wished for a system where FKs could be used to automatically mark rows as invalid instead of deleting them, and you could inspect the nature of the broken reference as a property of the row/object. Then broken references can be cleaned up when appropriate, possibly never depending on the application.
This gives the neat property of being able to do data entry in parallel, too - different people may insert records into two tables linked by a FK relationship, it's nice for this to happen in either order. It also allows the user to query for exactly what rows will be affected by a cascaded delete, or to perform the operation in steps.
Wouldn't you effectively get those features by just not using FKs? You'd get your broken-reference marker by `where foreign_id not in (select id from foreign_table)`. You could create that as a view or materialized view.
It would be nice to have the schema metadata, at the very least, to be able to analyze a given tables reverse dependencies without resorting to naming conventions.
That's fine for storing, the problem is that you need the key to sign any tx, so if you just have the paper wallet you need to import it to a computer or mobile device each time you need to do it while if you have an hw device the key never leaves it
There are also tools that allow to take your seed and split it in m subgroups so that you need at least n out of m to rebuild it. So instead of giving password to a single family member (or two relatives, half and half) you can give it to more people and you can still recreate it even if some lose it
Totally agree with you. Even if you have delayed copies, you still need proper backup in place.
They recently implemented long term retention for Azure SQL backups in Azure: https://azure.microsoft.com/en-us/blog/azure-sql-database-no... as it was only allowing 'til 35 days.
I would expect that something similar is provided also for this type of DBs
One can hope. Blob and table storage still have no form of backup ~8 years after introduction.
When I've asked they have been referring to replication and to call them if we accidentally lose data. But we need to contact them within two hours otherwise it's too late. And of course Azure Support never responds that quickly when I submit a case to them.
4-5 years ago I used pfsense as internet gateway and vpn for point to point in an office with probably 20-30users.
We had it clustered between a VM (on ESXi) and a physical appliance on alix (if I recall correctly, or another of the supported sff appliances). The VM was rock solid while the appliance from time to time was experiencing issues (stuck/memory exhausted I think) up to the point that DHCP lease were not released anymore and the office was de facto unable to work.
I think at the end we just kept the VM running alone.
What makes my suspicious is that I can't find any information on the company itself anywhere on the site. Where are they headquartered? What's their contact information? It's not even clear under what jurisdiction they operate.
Again, we had all of this in place prior to an ill-advised website redesign.
As I said higher up in this thread, I'll make sure this gets republished and put in place properly today and I will add some verbiage that addresses your specific point about HQ and jurisdiction.
In the meantime, I will confirm we are a US firm with locations (ie., our own racks - not rented hardware) in San Diego, Fremont (San Francisco, basically), Denver, Zurich and Hong Kong.
Phys-sec means you don't just advertise your location, and keeping control over how people can contact you is another way to prevent social engineering attacks.
AFAIK almost all the glasses frames are worth few dollars. What you pay for branded ones is marketing and bit of design, not generally the material quality.
