On Sunday 18 October 2015 06:51 PM, bobhaugen wrote:
krmane, are you posting these same questions in the REST framework forum?

I'm guessing they would like a SQLAlchemy plugin.
If such a plugin does exist it is great.

Unlike you, however, I like their documentation, and have found the DRF gang to be responsive to issues. That being said, I haven't actually used it in production yet. Just experimenting. I too don't find the documentation bad or unorganized, just that there are some situations not covered.
And I feel enough time should have been given to explain fundamentals of serializers or viewsets. For example no matter which ORM I use, I do not totally rely on the Object mapping in any big project. The approach I take is to use ORM for small result sets and using sqlalchemy expression language for big tasks. Data objects have an overhead and the convenience comes at a cost of speed for huge data such as those with more than 50000 records and that too when queries are complex enough.
Of course I will write to them in a short while.
happy hacking.
Krishnakant.
On Saturday, October 17, 2015 at 9:28:33 AM UTC-5, krmane wrote:

    Hi again,
    Xavier, I have gone through the main DRF documentation and also
    seen your blog.
    I am wondering if you can send me an off line email which can
    explain the relation between serializer and viewset?
    I have not got the concept clear, I am beginner to REST and all I
    understand is that the response is generally in form of json.
    happy hacking.
    Krishnakant.


    On Friday 16 October 2015 03:39 PM, Xavier Ordoquy wrote:
    Hi,

    I wrote a short blog post about getting most of Django REST
    framework without using Django models.
    
https://medium.com/@linovia/django-rest-framework-viewset-when-you-don-t-have-a-model-335a0490ba6f
    
<https://medium.com/@linovia/django-rest-framework-viewset-when-you-don-t-have-a-model-335a0490ba6f>

    You will loose the integration with the Django Models and will
    need to do a few things by yourself (pagination for example) but
    it’s still perfectly possible to do that.
    Note that most of the documentation covers Django Models because
    it’s where most of the options are. When you don’t use them, it’s
    up to the developers to provide the content which will be very
    different from a project to another.

    Hope this will help,

    Regards,
    Xavier,
    Linovia.


    Le 16 oct. 2015 à 12:00, kk <krm...@gmail.com <javascript:>> a
    écrit :

    hello again,
    I haven't got my doubts solved but a few got added.
    I was again going through the tutorial on Django REST framework.
    I am trying to know if I can use a serialiser without tying it
    to the DJango ORM or for that matter without tying it to any thing?
    I prefer using SQLAlchemy and get the data out using sql
    expression language.
    Then I would like to convert this data to json format for
    sending as response.
    Is this possible?
    Happy hacking.
    Krishnakant


    On Friday 16 October 2015 11:39 AM, kk wrote:
    Dear all.
    I got some very important suggestions from members of this list
    on using Django for an accounting and inventory system,
    including Point of Sale.
    After the POS topic was discussed,
    OUr team decided to write a RESTfull server with all the
    business logic in API.
    We plan to do this using some thing like Flask micro framework
    and then write a complete web app using Django to consume these
    services.
    Of course it could be argued that why not use Django REST
    framework?
    But here I am a bit surprised as well as a bit disappointed.
    Contrary to what we have all seen and experienced about
    Django's documentation, the rest framework is not at all
    comprehensively documented.
    I am still not totally understood the use of
    |serializers.HyperlinkedModelSerializer. viewset is also not
    totally explained properly. the tutorial is pretty fast and
    confusing. I think a better example would have served it more
    understandable. Or perhaps the documentation there asumed that
    every one who reads it is a Django as well as REST expert, even
    then it is confusing. Any ways coming back to the topic. So
    What suggestions could I get about my main query? happy
    hacking. 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
    django-users...@googlegroups.com <javascript:>. To post to this
    group, send email to django...@googlegroups.com <javascript:>.
    Visit this group at http://groups.google.com/group/django-users
    <http://groups.google.com/group/django-users>. To view this
    discussion on the web visit
    https://groups.google.com/d/msgid/django-users/5620CACC.2060702%40gmail.com
    
<https://groups.google.com/d/msgid/django-users/5620CACC.2060702%40gmail.com>.
    For more options, visit https://groups.google.com/d/optout
    <https://groups.google.com/d/optout>.
    -- 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
    django-users...@googlegroups.com <javascript:>. To post to this
    group, send email to django...@googlegroups.com <javascript:>.
    Visit this group at http://groups.google.com/group/django-users
    <http://groups.google.com/group/django-users>. To view this
    discussion on the web visit
    
https://groups.google.com/d/msgid/django-users/9872C498-CD0B-44A3-B64E-62A34F312C02%40linovia.com
    
<https://groups.google.com/d/msgid/django-users/9872C498-CD0B-44A3-B64E-62A34F312C02%40linovia.com>.
    For more options, visit https://groups.google.com/d/optout
<https://groups.google.com/d/optout>.

-- 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 django-users+unsubscr...@googlegroups.com <mailto:django-users+unsubscr...@googlegroups.com>. To post to this group, send email to django-users@googlegroups.com <mailto:django-users@googlegroups.com>. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/730ad048-30e4-4c15-95b0-b76c2ee2d582%40googlegroups.com <https://groups.google.com/d/msgid/django-users/730ad048-30e4-4c15-95b0-b76c2ee2d582%40googlegroups.com?utm_medium=email&utm_source=footer>. For more options, visit https://groups.google.com/d/optout.

--
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 django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/56247F37.3050207%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to