Aaron Swartz wrote: > Nothing is stopping you from using whatever ORM you like best. > Understand, and the simplicity and flexibility is what we like about webpy versus so much extra baggage on frameworks like Django.
But we still need some more abilities such as looping thru data sets more than once in some involved reports. 1)is there a way to do that with webpy (I guess somehow write out to an array and pass the whole array even if that's less efficient than iterators, ie the PHP way) 2) if not easily done, would an ORM really help us on that and if so, is there one which "fits" best with webpy ? I also wonder if webpy is really the right tool if we'll have 50-100 tables with lots of joins, etc - we have already created a separate "model.py" with methods for common lookups. We have been also prototyping with Rails and that seems to work but comes with all that extra "rails and ruby way" stuff which drives us a bit crazy. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
