Hello, afaik, nothing forces you to use SQLAlchemy with Pyramid (after all, you could decide to use a non-relational database such as the ZODB or MongoDB).
If you are sure that you won't need database attraction later, you can talk to psycopg2/3 directly. By doing so, you will also lose the possibility to automatically synchronise SQL transactions with Pyramid. It may or may not be ok for you, depending on your problem, but it's certainly possible to implement the required mechanism if required. On the other hand, you might decide to run your raw SQL queries via SQLAlchemy, without using the ORM parts. This would give you the transaction synchronisation, provided you remember to mark your DB session as changed (look for "mark_changed" in https://pypi.org/project/zope.sqlalchemy/#full-example) after an insert/update/delete query. Hope this helps, Laurent. Le jeudi 11 août 2022 à 17:53:31 UTC+2, [email protected] a écrit : > Hello , > > I am building an application ( more of a tool really ) that have a web > interface , and I am trying to avoid using ORM all together. plus I want to > try postgresql features and experiment more with them. > > I don't want things to be overly complicated on the web interface so I put > lots of logic , *something that I know will not change any time soon* , > into PostgreSQL directly using functions etc. > > can you please point me to the right direction of using pyramid without it > ? what might be the pitfalls of not using an ORM with pyramid ? > > > > Thanks ! > -- 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/a7710dbe-768b-452c-bfb8-e4bbfad95854n%40googlegroups.com.
