🚀 PostgreSQL pro tip: You can make columns auto-compute themselves 👇 CREATE TABLE users ( first_name text, last_name text, full_name text GENERATED ALWAYS AS (first_name || ' ' || last_name) STORED ); 💡 Auto-updates when data changes ⚡ Indexable 🧠 No triggers
API design is 70% planning and structuring the database, 20% implementing the routes, and 10% testing to make sure everything actually works. #APIs
App idea: A simple notes app that fits your lifestyle, summarizes your thoughts, reminds you when needed, and helps you learn in your own way. No matter if you're a programmer, student, designer, or just trying to stay organized, it's made for you. #ai #startupcommunity
0.1 + 0.2 in JavaScript 👀 console.log(0.1 + 0.2) // 0.30000000000000004 ⚠️ Binary floats can't store 0.1 exactly ⚠️ Happens in most languages, not just JS ✅ For money: use integers (cents) ✅ For comparisons: check if difference < 0.00001
PostgreSQL MONEY type 👀 ⚠️ Formatting depends on locale settings ⚠️ Only handles one currency per database ⚠️ Limited math operations NUMERIC(19,4) is more common now: ✅ Precision control ✅ Works with any currency ✅ Better for calculations
EXCLUDED in PostgreSQL 👀 References the row you tried to insert during conflicts: INSERT INTO stats (id, views) VALUES (1, 5) ON CONFLICT (id) DO UPDATE SET views = stats.views + EXCLUDED.views; ✅ Increment instead of replace ✅ Cleaner upserts ✅ Access attempted values
satisfies in TypeScript 👀 Checks types but keeps literal values: const routes = { home: '/', user: '/user' } satisfies Record<string, string> ✅ Type validation ✅ routes.home stays '/' not string ✅ Better than 'as' casting
Gapless IDs 👀 ✅ Ticket table with SELECT ... FOR UPDATE Example: UPDATE tickets SET id = id + 1 RETURNING id; ✅ Manage sequencing in application logic with proper locking (e.g. Redis INCR or a mutex) ⚠️ Keep in mind: gapless IDs = higher contention + slower writes
PostgreSQL SERIAL creates gaps when transactions fail 😵 If you need gapless IDs, don't use SERIAL 🚫 Only use it when gaps are fine 👍 Next: better ways to handle sequential IDs 👀
PostgreSQL SERIAL creates gaps when transactions fail 😵 If you need gapless IDs, don't use SERIAL 🚫 Only use it when gaps are fine 👍 Next: better ways to handle sequential IDs 👀
if you vibe with typescript + backend + postgresql, hit follow 👀 posting dev stuff from tomorrow, let’s ship 🚀 #typescript #OpenSource
United States 趨勢
- 1. #JoyForum 1,300 posts
- 2. #2025MAMAVOTE 211K posts
- 3. Good Thursday 18.2K posts
- 4. Brevis ZK 136K posts
- 5. Mila 17.5K posts
- 6. Deport Harry Sisson 11.9K posts
- 7. #MC필릭스의_냉터뷰 11.8K posts
- 8. MC FELIX FRIDGE INTERVIEW 12.8K posts
- 9. #FridgeInterview_MCFelix 12K posts
- 10. Friday Eve N/A
- 11. #2025MAMAAWARDS 182K posts
- 12. Tomonobu Itagaki 6,228 posts
- 13. BNB Chain 20.3K posts
- 14. Deloitte 8,804 posts
- 15. Ninja Gaiden 10.4K posts
- 16. DuPont 2,039 posts
- 17. Pelosi 145K posts
- 18. Angel Reese 56.1K posts
- 19. Mad Max 4,318 posts
- 20. John Fetterman 28.1K posts
Something went wrong.
Something went wrong.