> this may be not a very popular opinion, but I prefer to design the database without using database-specific features I used to be in this camp, having starte

> this may be not a very popular opinion, but I prefer to design the database without using database-specific features I used to be in this camp, having started my dev life in Rails when it ran Sqlite in dev. This turned out to be an anti-pattern for Rails because dev/prod parity was never quite there. Over time I also realized it just wasn't worth the effort to keep things agnostic. Sure a hypothetical migration will be easier later on, but that migration very, very, very (very) rarely occurs in my experience.