Postgres DDL has a huge advantage over MySQL for transactional support.
Most CREATE, ALTER, and DROP statements in Postgres are first-class citizens in multi-statement transactions. This means you can use them between BEGIN and COMMIT and all changes will either succeed or fail atomically along with all other statements.
This is not true in MySQL. Such statements use an implicit commit model. Whenever a CREATE, ALTER, or DROP statement is executed, it implicitly commits whatever transaction it is a part of.
This means in Postgres, you can do things like:
- Create a table + insert data as a single atomic action
- Modify multiple tables atomically
وش الأماكن اللي تمرّ جنبها يوميًّا وما قد وقفت عندها؟ 🤔
خلّنا نعرّفك على الرياض من زوايا مختلفة وندلك على أماكن يمكن ما شفتها من قبل
قيّم ⭐
صوّر 📸
وشارك بطريقتك 🗨️
لأن تجربتك، هي اللي تكمل القصة ❤️
#خرائط_هدهد
@ethanniser Hey Ethan, Effect noob here. trying to load .env and validate it and add it as a Content Layer, but I got lost between loading via PlatformConfigProvider.fromDotEnv using Schema or Config for validation and creating the layer via setConfigProvider. any advice?