Accurate record-keeping (certainty in data)

The 'blockchain' is popular because it's the first 'database' to provide certainty in data. Accurate record-keeping.

Currently, all databases can be changed without trace. It's up to the DBA and internal policy to prevent it.

Therefore, we need standards. I have suggested standard #1 of Load/Store/Delete/LoadList as a universal external interface. No one paid any attention.

You're going to lose your jobs if this isn't solved.

What can we do today to ensure data is accurate?

maybe this?

Database.Load(customer);
Database.Store(customer);
Database.Delete(customer);

:wink::thinking:

1 Like

All external access must go through stored procedures. SQL is not allowed outside the database.

Let it go Andrew

Cities to issue email addresses connected to property address. Identity.