On Apr 18, 2007, at 12:03 PM, Mike Orr wrote: > Great idea. Pylons definitely needs a database administration tool. > My main concern is about basing it on the ORM layer rather than > accessing tables directly. The application I'm working on now uses > SQLAlchemy for its auto-retry connections and SQL builder, but I found > the ORM to be unnecessary complexity for it. Could AdminPylon support > both ORM and non-ORM interfaces?
I believe that would add a significant amount of redundant complexity to this, as SA has already abstracted and done a ton of introspection work that would need to be done yet again. Adding stuff like this will bring necessary requirements on other tools, which is why its place is not in Pylons itself, but in additional tools, and I think that's just fine. ;) I'm looking forward to AdminPylon getting fleshed out a bit. Cheers, Ben --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
