Hello. Some questions. Walking through projects on github i found django-save-the-change[1]
Interesting project. But what django-save-the-change[1] proposes to do is still valid for Django 1.7? I think it would be good practice to only touch in the fields in the database in which there really was a change. Using or not using this solution, makes difference in performance when I have millions of transactions per minute in the database? [1] https://github.com/karanlyons/django-save-the-change -- Fábio C. Barrionuevo da Luz Acadêmico de Sistemas de Informação na Faculdade Católica do Tocantins - FACTO Palmas - Tocantins - Brasil - América do Sul http://pythonclub.com.br/ Blog colaborativo sobre Python e tecnologias Relacionadas, mantido totalmente no https://github.com/pythonclub/pythonclub.github.io . Todos são livres para publicar. É só fazer fork, escrever sua postagem e mandar o pull-request. Leia mais sobre como publicar em README.md e contributing.md. Regra básica de postagem: "Você" acha interessante? É útil para "você"? Pode ser utilizado com Python ou é útil para quem usa Python? Está esperando o que? Publica logo, que estou louco para ler... -- 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 post to this group, send email to [email protected]. 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/CAPVjvMaHL_wEAd-widOC3wxv%2BHcivCP47USMoEMHg5jm9Dmssg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
