Currently for things like this I create a view and serializer that are not
related to any model.
Of course I lose some introspection code that expect a model, but for the
most part I'm able to make an API endpoint with data not from the ORM.
Can you elaborate more on your use case?
On Thu, Mar 2
I have this recurrent need that I handle entities that are not tables but
calculated entities from other models.
Consider this example :
an entity that I call task that is calculated using the model suggestion a
task may be to approve a suggestion, to pilot a suggestion, to close a
suggestion
2 matches
Mail list logo
