postgresql

Introduction I work for Vertalo, a digital transfer agent — in short, we make the magic happen for the transfer of digital assets, such as tokenised securities, by maintaining and updating ownership records. Of course, having a robust, powerful, and well-designed database is critical. We have to organise and manage information about clients, issuers, transactions, and so much more. Traditional tools to facilitate working with databases include visualisations such as Entity-Relationship Diagrams (ERDs), but these suffer from two large caveats: first, they often require manual construction and updates, making them impractical for large and evolving databases. [Read More]

The PostgreSQL documentation has this to say in the context of constraints: The NOT NULL constraint has an inverse: the NULL constraint. This does not mean that the column must be null, which would surely be useless. Instead, this simply selects the default behavior that the column might be null. The NULL constraint is not present in the SQL standard and should not be used in portable applications. Of course the description of the NULL constraint is correct, however requiring that a column must be null does in fact have utility! [Read More]