Explore >> Select a destination
|
You are here 
|
buttondown.com | ||
| | | | |
stribny.name
|
|
| | | | | A list of things that we can do when we need to scale a SQL database. | |
| | | | |
hashrocket.com
|
|
| | | | | PostgreSQL 18 introduced a powerful new feature that lets you enforce uniqueness across time periods: Temporal Constraints. With this addition, you can now define UNIQUE, PRIMARY KEY, or FOREIGN KEY constraints by either Date Range or Timestamp Range fields, making it easier than ever to prevent overlapping data. | |
| | | | |
antzucaro.com
|
|
| | | | | The Scenario Let's suppose you are modeling a database in MySQL 5.5. Based on your knowledge of the requirements for the application behind this database you can guess which of the tables within it are going to be huge. For those huge tables you want to plan ahead to make sure that you can scale out your data such that you have less headaches in the future. Here's the catch: you want to keep it simple until it comes time to scale out. | |
| | | | |
libresolutions.network
|
|
| | | Don't overlook the importance of backups! | ||
