> Furthermore, in the general case, business logic is too complex to be > implemented simply in the database layer - significant business logic > would need stored procedures, triggers etc. which are inherently non- > portable across RDBMS platforms.
Portability across RDBMS platforms is a pipe dream for anything except "happy apps". Forgive me for creating a serious database. If no-one here wants to talk to me about Django functionality, I'm not going to hang around. See you all, and thanks for the time you've taken to write your responses. On May 10, 5:25 pm, Vinay Sajip <[EMAIL PROTECTED]> wrote: > On May 10, 7:37 am, foobarmus <[EMAIL PROTECTED]> wrote: > > > 1. RDBMSs like PostgreSQL, Oracle, perhaps even MySQL although it's > > still a fledgling in this regard (to name but 3), were designed to (or > > have subsequently been revamped to) handle the kind of business logic > > that large organisations demand. Web frameworks like Django invariably > > are not designed to handle such business logic. This is not a > > I'm probably misunderstanding something, but surely business logic is > the province of your application, and not of Django itself. > Furthermore, in the general case, business logic is too complex to be > implemented simply in the database layer - significant business logic > would need stored procedures, triggers etc. which are inherently non- > portable across RDBMS platforms. Also, in some scenarios, business > logic encompasses things which are not easily embeddable in the > database layer (e.g. sending out notification emails in a workflow > process). While Django is more focused on a model-driven approach from > which it works out and executes the SQL you need, there's no reason > you can't just use the urls and views part of Django and use e.g. DB- > API directly and provide complex business logic via code called from > your views. If you are using Django models, the model managers seem to > be the right place to put this kind of logic. > > Although Django does not yet provide all the hooks that are desirable > for some business needs - (e.g. support for views and stored > procedures and schema migration, a more generic authorization scheme) > it looks as if there is work in various branches towards providing > more functionality in at least some of these areas. > > My 2ยข, > > Vinay Sajip --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
