On Feb 14, 2009, at 3:40 PM, adelevie wrote: > > I'm someone who has been spoiled by Django's ORM. It's so simple > compared to the others. I tried learning SQLAlchemy and found that > there was so much extra stuff to code that didn't really pertain to my > models. All I want is to define models, attributes (and datatypes) and > foreignkeys. I'd be willing to contrib my noob skillz to making such a > library if anyone with more expertise is on board.
I don't know for sure, but I imagine porting Django's ORM to web.py would be relatively easy. Both web.py and Django use the same libraries to talk to the database. But, once you go down this road, what other things are you going to want to port from Django? newforms? Why then would you use web.py and not just use Django? > On Feb 13, 5:47 pm, bloofa <[email protected]> wrote: >> On Feb 5, 5:52 am, Stuart Colville <[email protected]> wrote: >> >>> If you're using sqlalchemy you may want to look at form >>> alchemyhttp://code.google.com/p/formalchemy/ >> >> Thanks, this looks interesting. As Adelevie said though, >> sometimes it >> would be good to avoid SQL Alchemy for simple database structures. > > -- http://www.apgwoz.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
