Hi. I've been coding in python recently and I'm interested in working with Django, partly because of my delight in working with python and partly due to a star-struck admiration for Ruby on Rails, 'sensible urls' and ORMs.
What I'm looking for is some general advice. What is at stake is a reasonably complex site in multiple EU languages which will require some fairly involved computations and, as ever, a painfully short development timetable. At the moment we have our own PHP/Postgres development framework featuring: 1. Postgresql 8/8.1 pl/pgsql functions with create/edit/delete objects relating to PHP single object entities 2. a PHP testing framework for objects and pg/pgsql functions 3. Postgres functions returning rows, often using UNIONS, LEFT OUTER JOINS, etc., mapping to PHP objects returning view-type collections of rows. 4. Smarty templating 5. controller logic which, functional programming style, decides where in the manipulate model/view model one needs to be. I'd be hugely grateful for advice on how suited Django might be to integrating with custom-written pl/pgsql queries, stuff that running the Django test tutorial does not answer. I imagine mapping python objects to pl/pgsql functions by hand yet benefit from URL mapping, cookie handling/session management (like PHP) and easy templating. I guess it is fair to say we would wish to discard the standard ORM mappings. Is this doable? Thanks for any comments and advice Rory -- Rory Campbell-Lange <[EMAIL PROTECTED]> <www.campbell-lange.net> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
