Geobase Isoscale kirjoitti: > I have to live with this reality, maybe in future we might develop a > code to extend Django to support views and triiggers.
I don't get the use case here. What is this need for adding views and triggers? What purpose they serve for ORM? For database they're pretty handy to do business logic if there is data incoming form external resources that are not passed through ORM that can take care of all that mess but this can already be done with Django. There is (standard) way to add arbitary SQL scripts that are ran after django tables and such are generated or it can be done quite easily manually. Could you provide some examples what you're trying to achieve to shed some light here..? -- Jani Tiainen --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
