All geek questions in one place

If I plan to use MySQL, and if speed is a priority, is there any convincing reason to use SQLAlchemy?

SQLAlchemy seems really heavy if I use MySQL.

Why are there compelling reasons / against using SQLAlchemy in an application that uses MySQL.

+3
source share
3 answers

ORM means that your OO application really makes sense when interpreted as an interaction of objects.

No ORM means that you should wallow in the impedance mismatch between SQL and objects. Working without ORM means a lot of redundant code for matching sets of SQL query results, individual SQL statements, and objects.

SQLAchemy breaks your application into objects that interact and the persistence mechanism, which (today) is a relational database.

With SQLAlchemy, you have the chance to merge the main model and handle odd constraints and quirks of SQL RDBMS.

+7
source

I do not think that performance should be a significant factor in your choice. The level added by ORM will be negligible compared to the speed of the database. Databases eventually become a bottleneck.

ORM . , , ORM.

+4

sqlalchemy , , /// , ..... sql SQL- . , .

, , , sql .

0

Source: https://habr.com/ru/post/1734943/

More articles:


All Articles