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 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 orm.
Django-ninja looks promising.
On Sat, Jul 13, 2024 at 9:15 PM Krishnakant Mane <[email protected]>
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 are accounting rules (Debit = Dr and credit = Cr) for double
entry book keeping.
Every transaction will have 2 or more amounts, at least 1 each for
dr or
Cr.
These entries are called vouchers.
We also store retail bills, receipts and payments again all in
different
tables.
But the bills and receipt&payment tables are connected to the voucher
table.
The software generates reports such as cash flow, meaning day's
opening
balance, total Drs, total crs, and final closing balance (DRs - Crs).
then there are Profit and Loss as well as balance sheet reports.
All this needs a lot of aggregations (sum and counts ) and also
joining
of invoice + voucher and recept&payment + voucher tables.
so here are my questions.
1: given the fact that I have created materialised views in
Postgresql,
should I even care to model them and use the ORM syntax instead of
raw
query? What would perform better?
2: datasets are going to be huge some times in terms of shear rows
(all
transactions aka vouchers ) or some times sum and count will be
used in
complex queries on a huge dataset.
Again, should I rely on raw queries or will ORM plan the queries
for me
better? Should I instead create stored procedures and call them
from my
REST API?
talking of which,
3: I am using Django REST Framework and serialising records is an
option
to get json output.
Should I use it or just go with raw queries and convert output to
JSON
as required?
Again performance is a question.
Tip, My team is very proficient in SQL and yours truely can modestly
call himself an expert in the same, so maintenance is not an issue
here.
Regards.
Krishnakant.
--
You received this message because you are subscribed to the Google
Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected]
<mailto:django-users%[email protected]>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/097a6e55-c30e-491e-bf43-86e4c672faa4%40gmail.com.
--
You received this message because you are subscribed to the Google
Groups "Django users" 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/django-users/CALmEK1sEN%2BLjwcrT-7eYbQkrdkU2bynGehBo4BjvkW1NEBVUjQ%40mail.gmail.com
<https://groups.google.com/d/msgid/django-users/CALmEK1sEN%2BLjwcrT-7eYbQkrdkU2bynGehBo4BjvkW1NEBVUjQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups "Django
users" 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/django-users/f1a8a082-61c9-449c-9361-d1c8d77c0b07%40gmail.com.
