From 285319e77935751febfabae1ec2bd55a3455ea2c Mon Sep 17 00:00:00 2001 From: Ondrej Valenta Date: Thu, 8 Feb 2024 10:03:54 +0100 Subject: [PATCH] Update README.md --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index db5f0e1..fe38a89 100644 --- a/README.md +++ b/README.md @@ -4,10 +4,10 @@ db-gen is a universal tool for generation of function calls to PostgreSQL databa ## Is this tool an ORM framework? -No, this tool is no ORM framework in sense of C# Entity Framework, Elixir Ecto, PHP Doctrine and so on. In our experience, these full ORM tools are not worth it, they are usually clumsy, generate inefficient SQL code and lead programmers to dead ends. -Typical example of inefficent database use is when you want is a multi step processing of imported data. Instead of one bulk copy and a single database call to process the data, you have to split your logic to multiple database calls. It's slower, more work and usually less safe. +No, this tool is not an ORM framework in sense of C# Entity Framework, Elixir Ecto, PHP Doctrine and so on. In our experience, these full ORM tools are not worth it, they are usually clumsy, generate inefficient SQL code and lead programmers to dead ends. +Typical example of inefficent database use is when you want a multi step processing of imported data. Instead of one bulk copy and a single database call to process the data, you have to split your logic to multiple database calls. It's slower, more work and usually less safe. -That's why we use stored functions/procedures in PostgreSQL and this tool just generate code that calls these functions/procedures and retrieves the data. +That's why we use stored functions/procedures in PostgreSQL and this tool just generates code that calls these functions/procedures and retrieves the data. ## What issues this tool tries to address? - consistency of generation over years