2009/1/21 Jan Koprowski <[email protected]>: > > Ok. I understood this. But - i must wrote this methods. Simple CRUD > isn't something bad. SQLAlchemy could support something like this: > > class User(SQLAlchemy.CRUD): > pass > > > and give optionaly something like in django. This will be nice... > > [snip] > > > IMHO this could be standard for all classes (why not). I understood > this SQLAlchemy forces you to write your own class methods wrap > meta.Session - but this isn't cool :P because i waste my time :P >
I think others have pretty much drove the point home, but the reason you think it's "more work" is because SA does X well, and you want it to do Y. We can argue the point of X vs. Y, but ultimately it's your decision. Perhaps you should check out elixir... http://elixir.ematia.de/trac/wiki --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
