oracle

Sometimes it is needed to store compressed data in the DB. Unfortunately not all the DBs have built-in compression and FUSE compressed FSes are not available for every OS. So it may make sense to store compressed binary blobs in the DB.

Unfortunately when one sees them in DBeaver he sees them compressed, but often they are needed uncompressed. So it'd be nice to have a feature to decompress the

Right now, the API will (correctly) error with a foreign key constraint violation when deleting a user that has one or more uploaded images. I think it makes more sense to nullify the 'uploaded_by' field when you delete the user.

When implementing this in a new migration, we should also look into any other system tables that have a foreign key constraint to directus_users to ensure they all rel

Environment

Liquibase Version:
4.1.0
Also latest master

Liquibase Integration & Version:
gradle, unknown version

Liquibase Extension(s) & Version:

Database Vendor & Version:
PostgreSQL: 12.X (occurs on all supported versions)

Operating System Type & Version:
MacOS 11.4 (20F71), but will occur on all supported OSs

Description

A clear and concis

Description
Add a contract similar to Aave's AddressProvider or Uniswap's getPair() functionality.

Motivation
On-chain lookups of price oracles given the asset addresses.

Justification
String manipulation is difficult and expensive in Solidity, and you usually work with the token address, not its string name.

During migration of old sync code to async discovered that we don't have async versions of some API.