Model-less views with dynamic rest
up vote
0
down vote
favorite
Here is a very good description on how to implement model-less views with django-rest-framework.
How can we do the same with the dynamic-rest extension the the django-rest-framework?
django django-rest-framework dynamic-rest
asked Nov 8 at 6:48
dangonfast
13k23118220
|
show 1 more comment
up vote
0
down vote
favorite
Here is a very good description on how to implement model-less views with django-rest-framework.
How can we do the same with the dynamic-rest extension the the django-rest-framework?
django django-rest-framework dynamic-rest
asked Nov 8 at 6:48
dangonfast
13k23118220
DRF is all about optimizing Django's query performance, so without more information I'm not sure this makes obvious sense...
– thebjorn
Nov 8 at 7:26
@thebjorn: DRF is not only about db access, but also about providing a normalized REST interface: standard way of doing filtering, urls, pagination, an API UI, documentation, ... DB access is just one of the features covered by drf (and it is actually mostly based on django core functionality). In my specific case, I want to make use of DRF features (and dynamic rest, that's why I am asking), but the data at a specific endpoint is not backed by a database, but computed. I want to offer read capabilities to this data within the context of drf/dynamic-rest.
– dangonfast
Nov 8 at 7:35
@thebjorn: besides, the link I provided provides an example of a usecase when would you want to use DRF without database-backed data (in-memory data). Other use cases would include data computed from other DB models (as is my case), or data collected from other services via REST interfaces.
– dangonfast
Nov 8 at 7:40
Sorry, I meant Dynamic Rest when I said DRF (it's early still..).
– thebjorn
Nov 8 at 8:07
@thebjorn: well, then not really. :) Dynamic REST is intended to provide "Dynamic API extensions for Django REST Framework". It is an interface spec, for both URL and json responses, including paginationg, filtering, sorting, ... It is not related to DB access per-se. The base classes are not tied to database models.
– dangonfast
Nov 8 at 8:41
|
show 1 more comment
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Here is a very good description on how to implement model-less views with django-rest-framework.
How can we do the same with the dynamic-rest extension the the django-rest-framework?
django django-rest-framework dynamic-rest
asked Nov 8 at 6:48
dangonfast
13k23118220
Here is a very good description on how to implement model-less views with django-rest-framework.
How can we do the same with the dynamic-rest extension the the django-rest-framework?
django django-rest-framework dynamic-rest
django django-rest-framework dynamic-rest
asked Nov 8 at 6:48
dangonfast
13k23118220
asked Nov 8 at 6:48
dangonfast
13k23118220
asked Nov 8 at 6:48
dangonfast
13k23118220
asked Nov 8 at 6:48
dangonfast
13k23118220
asked Nov 8 at 6:48
dangonfast
13k23118220
13k23118220
DRF is all about optimizing Django's query performance, so without more information I'm not sure this makes obvious sense...
– thebjorn
Nov 8 at 7:26
@thebjorn: DRF is not only about db access, but also about providing a normalized REST interface: standard way of doing filtering, urls, pagination, an API UI, documentation, ... DB access is just one of the features covered by drf (and it is actually mostly based on django core functionality). In my specific case, I want to make use of DRF features (and dynamic rest, that's why I am asking), but the data at a specific endpoint is not backed by a database, but computed. I want to offer read capabilities to this data within the context of drf/dynamic-rest.
– dangonfast
Nov 8 at 7:35
@thebjorn: besides, the link I provided provides an example of a usecase when would you want to use DRF without database-backed data (in-memory data). Other use cases would include data computed from other DB models (as is my case), or data collected from other services via REST interfaces.
– dangonfast
Nov 8 at 7:40
Sorry, I meant Dynamic Rest when I said DRF (it's early still..).
– thebjorn
Nov 8 at 8:07
@thebjorn: well, then not really. :) Dynamic REST is intended to provide "Dynamic API extensions for Django REST Framework". It is an interface spec, for both URL and json responses, including paginationg, filtering, sorting, ... It is not related to DB access per-se. The base classes are not tied to database models.
– dangonfast
Nov 8 at 8:41
|
show 1 more comment
DRF is all about optimizing Django's query performance, so without more information I'm not sure this makes obvious sense...
– thebjorn
Nov 8 at 7:26
@thebjorn: DRF is not only about db access, but also about providing a normalized REST interface: standard way of doing filtering, urls, pagination, an API UI, documentation, ... DB access is just one of the features covered by drf (and it is actually mostly based on django core functionality). In my specific case, I want to make use of DRF features (and dynamic rest, that's why I am asking), but the data at a specific endpoint is not backed by a database, but computed. I want to offer read capabilities to this data within the context of drf/dynamic-rest.
– dangonfast
Nov 8 at 7:35
@thebjorn: besides, the link I provided provides an example of a usecase when would you want to use DRF without database-backed data (in-memory data). Other use cases would include data computed from other DB models (as is my case), or data collected from other services via REST interfaces.
– dangonfast
Nov 8 at 7:40
Sorry, I meant Dynamic Rest when I said DRF (it's early still..).
– thebjorn
Nov 8 at 8:07
@thebjorn: well, then not really. :) Dynamic REST is intended to provide "Dynamic API extensions for Django REST Framework". It is an interface spec, for both URL and json responses, including paginationg, filtering, sorting, ... It is not related to DB access per-se. The base classes are not tied to database models.
– dangonfast
Nov 8 at 8:41
DRF is all about optimizing Django's query performance, so without more information I'm not sure this makes obvious sense...
– thebjorn
Nov 8 at 7:26
DRF is all about optimizing Django's query performance, so without more information I'm not sure this makes obvious sense...
– thebjorn
Nov 8 at 7:26
@thebjorn: DRF is not only about db access, but also about providing a normalized REST interface: standard way of doing filtering, urls, pagination, an API UI, documentation, ... DB access is just one of the features covered by drf (and it is actually mostly based on django core functionality). In my specific case, I want to make use of DRF features (and dynamic rest, that's why I am asking), but the data at a specific endpoint is not backed by a database, but computed. I want to offer read capabilities to this data within the context of drf/dynamic-rest.
– dangonfast
Nov 8 at 7:35
@thebjorn: DRF is not only about db access, but also about providing a normalized REST interface: standard way of doing filtering, urls, pagination, an API UI, documentation, ... DB access is just one of the features covered by drf (and it is actually mostly based on django core functionality). In my specific case, I want to make use of DRF features (and dynamic rest, that's why I am asking), but the data at a specific endpoint is not backed by a database, but computed. I want to offer read capabilities to this data within the context of drf/dynamic-rest.
– dangonfast
Nov 8 at 7:35
@thebjorn: besides, the link I provided provides an example of a usecase when would you want to use DRF without database-backed data (in-memory data). Other use cases would include data computed from other DB models (as is my case), or data collected from other services via REST interfaces.
– dangonfast
Nov 8 at 7:40
@thebjorn: besides, the link I provided provides an example of a usecase when would you want to use DRF without database-backed data (in-memory data). Other use cases would include data computed from other DB models (as is my case), or data collected from other services via REST interfaces.
– dangonfast
Nov 8 at 7:40
Sorry, I meant Dynamic Rest when I said DRF (it's early still..).
– thebjorn
Nov 8 at 8:07
Sorry, I meant Dynamic Rest when I said DRF (it's early still..).
– thebjorn
Nov 8 at 8:07
@thebjorn: well, then not really. :) Dynamic REST is intended to provide "Dynamic API extensions for Django REST Framework". It is an interface spec, for both URL and json responses, including paginationg, filtering, sorting, ... It is not related to DB access per-se. The base classes are not tied to database models.
– dangonfast
Nov 8 at 8:41
@thebjorn: well, then not really. :) Dynamic REST is intended to provide "Dynamic API extensions for Django REST Framework". It is an interface spec, for both URL and json responses, including paginationg, filtering, sorting, ... It is not related to DB access per-se. The base classes are not tied to database models.
– dangonfast
Nov 8 at 8:41
|
show 1 more comment
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53202709%2fmodel-less-views-with-dynamic-rest%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
DRF is all about optimizing Django's query performance, so without more information I'm not sure this makes obvious sense...
– thebjorn
Nov 8 at 7:26
@thebjorn: DRF is not only about db access, but also about providing a normalized REST interface: standard way of doing filtering, urls, pagination, an API UI, documentation, ... DB access is just one of the features covered by drf (and it is actually mostly based on django core functionality). In my specific case, I want to make use of DRF features (and dynamic rest, that's why I am asking), but the data at a specific endpoint is not backed by a database, but computed. I want to offer read capabilities to this data within the context of drf/dynamic-rest.
– dangonfast
Nov 8 at 7:35
@thebjorn: besides, the link I provided provides an example of a usecase when would you want to use DRF without database-backed data (in-memory data). Other use cases would include data computed from other DB models (as is my case), or data collected from other services via REST interfaces.
– dangonfast
Nov 8 at 7:40
Sorry, I meant Dynamic Rest when I said DRF (it's early still..).
– thebjorn
Nov 8 at 8:07
@thebjorn: well, then not really. :) Dynamic REST is intended to provide "Dynamic API extensions for Django REST Framework". It is an interface spec, for both URL and json responses, including paginationg, filtering, sorting, ... It is not related to DB access per-se. The base classes are not tied to database models.
– dangonfast
Nov 8 at 8:41