4 ms·
it saves a lot of reinventing the wheel
by fiftyacorn 7mo ago
it saves a lot of reinventing the wheel
- rockyj 7mo agoAnd at the same time, gives you a dozen of footguns. This is just a list for the gotchas in the "@Transactional" annotation - https://dev.to/closeup1202/8-spring-transactional-pitfalls-that-break-production-and-how-to-catch-them-all-258f https://dev.to/closeup1202/8-spring-transactional-pitfalls-t... Now read up on all the dozen of annotations. But yeah, we did not want to "re-invent the wheel".
- fiftyacorn 7mo agoIm comparing against node equivalent ORMs and find spring consistently better. Yeah ive got to read up on annotations - but when it comes to transactions its always worth revisiting them to check for changes
- tracker1 7mo agoMeh... await using cn = await pool.connect(); const records = await cn.query<MyType>` SELECT ... FROM ... WHERE ... `; for await (const record of records) { ... } Oh, spring is so much better...
- throwawey1234 7mo agoSpring version: var records = jdbcClient .sql("select * from posts") .query(Post.class) .toList(); records.forEach(p -> ...);
- tracker1 6mo agoI'm not seeing a RecordsRequestFactoryHandlerProviderFactory in there... maybe it's not as bad as I remember.
- throwawey1234 7mo agoHalf of those are not really an issue with the annotation and seem a bit contrived. Thankfully the company that wrote the article has a linter/warning product to help avoid those pitfalls.