On Tue, Oct 24, 2006 at 02:28:43PM +0200, Carlos Yoder wrote: > While I believe this mini tutorial on signals is great, I guess this > functionality would be better accomplished in the DB itself, via a > trigger.
There are, i think, three ways of doing what was asked for: 1- signals. Benefits: it works with all dbs (supported by django), the fields are sortable using the api. Drawbacks: you can't use non-django code to do data manipulation, the data is not normalized. 2- raw sql. Benefits: the data is normalized, you can use any app code to access the data. Drawbacks: sql is not fully portable, there is no current way to use the django api to sort by subquery results, it requires both sql and python knowledge to maintain. 3- triggers. Benefits: you can use any app code to access the data, the fields are sortable using the api. Drawbacks: less portable than vanilla sql, it requires even more sql knowledge to maintain, and the data is not normalized. In my mind, triggers are the least successful of those three options. Triggers have neither the portability benefits, nor the normalization benefits. But that's just my opinion. Most important is really recognizing the strengths and weaknesses of each approach, and choosing based on that. -johnnnnnnnn --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
