Re: Help deciding ORM VS raw SQL trade-off in Complex scenario

2024-07-27 Thread Krishnakant Mane
Talking about Ninja. I am actually trying to figure out how I can distribute my crud APIs in seperate python modules (one per model ) and make a package in my app. Then How all the routs can be imported in the project urls.py at once. Any suggestions? Regards. On 7/14/24 21:35, Sam Brown wr

Re: Help deciding ORM VS raw SQL trade-off in Complex scenario

2024-07-14 Thread ReynardSec
Hello, On Sunday 14 July 2024 at 09:03:38 UTC+2 eric paul wrote: In whatever way possible use the Django ORM for security purposes and also efficiency . Offtopic: There are certain issues worth keeping in mind, even if you are using an ORM: https://www.elttam.com/blog/plormbing-your-django-orm

Re: Help deciding ORM VS raw SQL trade-off in Complex scenario

2024-07-14 Thread eric paul
According to your scenario an accounting system is a more complex system that requires high performance. It can be written in any language but as the system grows some programming languages will experience performance issues python being one of them take a case like Dropbox which was originally wri

Re: Help deciding ORM VS raw SQL trade-off in Complex scenario

2024-07-14 Thread Singhal._.paras
Bro , Just go for it ! On Sun, 14 Jul, 2024, 22:58 Krishnakant Mane, wrote: > I am looking into ninja too. > > I guess I may be able to use SQLAlchemy seamlessly with it. > > Regards. > On 7/14/24 21:35, Sam Brown wrote: > > Im sure there are performance metrics out there to prove the ORM will n

Re: Help deciding ORM VS raw SQL trade-off in Complex scenario

2024-07-14 Thread Krishnakant Mane
I am looking into ninja too. I guess I may be able to use SQLAlchemy seamlessly with it. Regards. On 7/14/24 21:35, Sam Brown wrote: Im sure there are performance metrics out there to prove the ORM will not be the bottleneck. But I’ve never seen it slow things down when I’ve employed a timer

Re: Help deciding ORM VS raw SQL trade-off in Complex scenario

2024-07-14 Thread Gulshan Yadav
If you use ORM QUERY THEN IT IS VERY EASY TO SOLVE THIS ONE BY USING FOREIGN KEY OR MANY TO MANY RELATIONSHIP AND WHEN IF USER NOT RAGISTER THEN WE NEED TO ADD NON RAGISTER USER UNIQUE KEY FOR IDENTIFICATION AND AMOUNT WHICH ONE TAKE RECIEVE THE MONEY STORED IDENTIFICATION KEY IN PAYMENT TABLE AND

Re: Help deciding ORM VS raw SQL trade-off in Complex scenario

2024-07-14 Thread Sam Brown
Im sure there are performance metrics out there to prove the ORM will not be the bottleneck. But I’ve never seen it slow things down when I’ve employed a timer on operation Also, ive recently ran into some of the limitations of drf and am looking into moving to an api that can be less coupled with

Re: Help deciding ORM VS raw SQL trade-off in Complex scenario

2024-07-14 Thread eric paul
In whatever way possible use the Django ORM for security purposes and also efficiency . I won't recommend to use Raw queries if you don't know what you are doing On Sun, Jul 14, 2024, 7:34 AM Enock Deghost wrote: > 🙄 > > On Sun, 14 Jul 2024, 6:15 am Krishnakant Mane, > wrote: > >> Hello. >> >>

Re: Help deciding ORM VS raw SQL trade-off in Complex scenario

2024-07-13 Thread Enock Deghost
🙄 On Sun, 14 Jul 2024, 6:15 am Krishnakant Mane, wrote: > Hello. > > I am seasoned SQLAlchemy user and quite good in node's sequelise ORM. > > But I am new to the one with Django.So here's my situation. > > I am developing an accounting (book keeping ) automation software service. > > So there a