On Thu, Aug 11, 2022 at 9:54 AM pzzcc <[email protected]> wrote: > I want to avoid using SQLALCHEMY all together really to have a better > understanding of how things work inside pyramid for integrating the tool with > other tools already in place. so I think that is the correct route. once I > get this to work , I will have a deeper understanding of pyramid in general > which will help integrating that tool into the system we already have in place
If you get out of SQLAlchemy and the transaction manager, then you're getting out of Pyramid's database toolchains. I.e., you're DEintegrating, not integrating. What you'll learn is the low-level database API (psycopg2, based on Python's DBAPI interface). That's worth learning about if you like low-level close-to-the-metal tools. It can do simple tasks fine, but large abstract concepts or large development teams may do better with something high-level like SQLAlchemy. SQLAlchemy's creator, Michael Beyer, has given talks at several Pycons, and is friends with the people who created Pylons and Pyramid. He's a super-expert on SQL. So there's also value in benefiting from his expertise when you use SQLAlchemy, and when you look at how flexible SQLAlchemy can be. He also wrote the Mako template engine. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/CAH9f%3DupCUZ2DiVOb%3D7NSgJDbe1JLwOYFOkcjPMM8htsmL-Nduw%40mail.gmail.com.
