News for hackers. Stuff that matters.

A comment on 12 requests per second: A realistic look at Python web frameworks. Parent comment

Re:12 requests per second: A realistic look at Python web fr... by kaba0 on Friday February 19, 2021 @06:33AM (#26192004)
Yes, things like setString(1, “asd”) and conversely getInt(2) are so beautiful and will never introduce mistakes /s

ORMs are there for mapping objects and well, relations. Most ORMs provide additional features, but at the core they can, and for more complicated queries they should be used with native SQL queries. They are made for OLTP not for OLAP

[ Parent | on HN ]
Re:12 requests per second: A realistic look at Python web fr... by exyi on Friday February 19, 2021 @08:12AM (#26192749)
Like there wouldn't be anything in between /s

There are "simple ORMs" that only map results of SQL queries to objects. They do not provide a magic query API - which is the source of most problems. I don't do Python, but for .NET there is Dapper https://github.com/StackExchange/Dapper, you can have a look what I mean. You write the SQL query, explicitly execute it, the library maps the results of that query into objects (it's C#, so you have to declare the class. In Python I'd imagine it would create the object for you)

[ Parent | on HN ]
Re:12 requests per second: A realistic look at Python web fr... by jaywalk on Friday February 19, 2021 @10:04AM (#26193896)
+1 for Dapper. It does have some limited "magic" query building features, but only for straightforward CRUD operations that don't involve joins. And that's a Good Thing (TM).
[ Parent | on HN ]