Go in Production – Lessons Learned

Re:Go in Production – Lessons Learned by alexchamberlain on Saturday November 07, 2020 @02:43AM (#25013698)

Using SQLAlchemy has been my biggest (technical) regret in my current project; it was great at first, but overtime it's made testing a lot harder and session/object management has led to subtle bugs.

[ Parent | on HN ]

Re:Go in Production – Lessons Learned by danjac on Saturday November 07, 2020 @03:27AM (#25013814)

Getting Flask/Pyramid + SQLAlchemy + pytest to play nicely with sessions, transactions and rollbacks has often been the one thing that made me go "screw it" and start over with Django.

[ Parent | on HN ]

Re:Go in Production – Lessons Learned by jchw on Saturday November 07, 2020 @02:50AM (#25013713)

I feel like it’s a great tool to have available because it has solutions for everything you might want, but I found myself preferring it more for scripting than for application servers. Never quite figured out how to properly handle database sessions, really.

[ Parent | on HN ]

Re:Go in Production – Lessons Learned by ywei3410 on Saturday November 07, 2020 @04:50PM (#25019854)

Speaking from experience, session/object management is always tricky with ORM's. SQLAlchemy has been good for us; but the usage has been very, very disciplined and doesn't look idiomatic.

[ Parent | on HN ]