On Feb 24, 10:36 am, "Diez B. Roggisch" <de...@nospam.web.de> wrote: > > Thanks for all your suggestions. From what I've experienced in Django > > and now that I know a little more about how Python functions, I will > > probably use a combination of PHP and Django, instead of trying to get > > Python to do the web portion of my project. Thanks again! > > That sounds like the worst idea. Django's ORM is good when used from > within django, because of all the additional goodies like the admin > interface. > > But if you are going to do the webfrontend using PHP, what part is left > for django? If it's only the ORM (for whatever you still use that > anyway), there are better alternatives - SQLAlchemy, and SQLObject, for > Python. They are more powerful and not interwoven with django. > > If you are going to hand-code the interface in PHP, I fail to see though > why you don't do that in Django directly. You are not forced to use the > Admin-interface. > > Diez
Hello Diez, I think Django is fabulous for the admin-interface, a simple text search and template inheritance. I will use Django for all of those. What I'm not getting an answer to and cannot find an example of is a complex search, where I have to retrieve data from multiple tables, combine the data, remove the duplicates, etc between a web page and the database. The code that started this thread is only a small piece of the complex data retrieval I need to do. PHP is great for writing complex SQL queries right in the HTML template and I know exactly what it is doing. -- http://mail.python.org/mailman/listinfo/python-list