python - Advice on structuring a growing Django project (Models & API) -


i’m working on improving django project used internally @ company. project growing i’m trying make design choices before it’s unmanageable refactor. right project has 2 important models rest of data in database supports each application in project added database through various separate etl processes. because of majority of data used in application queried in each view via sqlalchemy using straight multiline string , passing data through view via context param when rendering rather using django orm.

would there distinct advantage in building models tables populated via etl processes can start using django orm vs using sqlalchemy , query strings?

i think makes sense start building api rather passing gigantic amount of information through single view via context param, i’m unsure of how structure api. i’ve read people create entirely separate app named api , make views in return jsonresponse. i’ve read others same view based api include api.py file in each application in django project. others use django rest api framework, seems simple more complicated returning jsonresponse via view. there 1 place users interaction data database , portion of project uses django rest framework perform crud operations. being said:

which of these api structures typical, , gain/lose implementing jsonresponse views api vs using django rest framework?

thanks in advance resources or advice has regarding these questions. please let me know if can add additional context.

would there distinct advantage in building models tables populated via etl processes can start using django orm vs using sqlalchemy , query strings?

yes, centralized, consistent way of accessing data, , of course, 1 less dependency on project.

which of these api structures typical, , gain/lose implementing jsonresponse views api vs using django rest framework?

in general terms, json used data, , rest apis. mentioned django-rest in use, if there's tangible benefit having rest api, i'd go it


Comments

Post a Comment

Popular posts from this blog

jOOQ update returning clause with Oracle -

according http://www.jooq.org/doc/3.8/manual/sql-building/sql-statements/update-statement/ jooq doesn't support returning clause in update statements databases except firebird , postgres. does know, still correct oracle jooq? according oracle's documentation, oracle db supports returning clase delete, insert, or update statements. incorrect manual you're right - manual wrong , should fixed: https://github.com/jooq/jooq/issues/5470 single row update returning jooq 3.8 added support single row update .. returning statements. internally, uses callablestatement , pl/sql block of form: begin update "my_table" set "my_table"."column" = 'xyz' "my_table"."id" = 1 returning "my_table"."id", "my_table"."column" ?, ?; ? := sql%rowcount; end; the relevant issue is: https://github.com/jooq/jooq/issues/5190 multi row update returning a...
Read more

java - Warning equals/hashCode on @Data annotation lombok with inheritance -

i have entity inherits other. on other hand, i'm using lombok project reduce boilerplate code, put @data annotation. annotation @data inheritance produces next warning: generating equals/hashcode implementation without call superclass, though class not extend java.lang.object. if intentional, add '@equalsandhashcode(callsuper=false)' type. is advisable add annotation @equalsandhashcode (callsuper = true) or @equalsandhashcode (callsuper = false) ? if not added, 1 callsuper=false or callsuper=true ? the default value false . 1 if don't specify , ignore warning. yes, recommended add @equalsandhashcode annotation on @data annotated classes extend else object. cannot tell if need true or false , depends on class hierarchy, , need examined on case-by-case basis. however, project or package, can configure in lombok.config call super methods if not direct subclass of object. lombok.equalsandhashcode.callsuper = call for configuration system ...
Read more

java - BasicPathUsageException: Cannot join to attribute of basic type -

i using java 8 jpa (hibernate 5.2.1). have clause works perfectly, until introduce clause make use foreign key table values too. i getting following error: basicpathusageexception: cannot join attribute of basic type i think problem related fact have join table, , not sure how create join using join table. employee - employee_category - category model (employee.java): @manytomany(cascade = cascadetype.all, fetch=fetchtype.eager) @jointable ( name="employee_category", joincolumns={ @joincolumn(name="emp_id", referencedcolumnname="id") }, inversejoincolumns={ @joincolumn(name="cat_id", referencedcolumnname="id") } ) private set<category> categories; model (category.java): @id private string id; jpa when introduce following code, fails error above (i think problem new piece of code): join<t, category> category = from.join("id"); predicates.add(criteriabuilder.like(category....
Read more