Commit bd4b30d5 authored by Shane A. Stillwell's avatar Shane A. Stillwell 🎯

Fix misspelling and remove weasel word

parent 81abf5cd
......@@ -47,7 +47,7 @@ We should address why auto-increment is a short sighted database design decision
1. **Uniqueness**: Auto-increment ids are NOT unique. Enough said I guess. This causes a problem when you may want to combine similar tables.
1. **Predictable**: Auto-increment ids are entirely predictable. If ids get exposed to outside operators, this will open act surfaces for bad actors, i.e. hackers love auto-incremented integers as ids.
1. **Predictable**: Auto-increment ids are entirely predictable. If ids get exposed to outside operators, this will open attack surfaces for bad actors, i.e. hackers love auto-incremented integers as ids.
### So, if I can't use auto-increment, what should I use?
......@@ -61,7 +61,7 @@ Some minor drawbacks to using a UUID
### How to use a UUID in PostgreSQL?
First, you'll need to add support for it. It's very likely your version of PG already has it ready at your finger tips, but you need to enable the following plugins when you design your database.
First, you'll need to add support for it. It's likely your version of PG already has it ready at your finger tips, but you need to enable the following plugins when you design your database.
```sql
CREATE EXTENSION IF NOT EXISTS "pgcrypto";
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment