Yoan Blanc wrote: > About "conversions", don't you think a module would be more > appropriate/pythonic? > My original idea was to have these methods in the model class - but I think you are right - any generic conversions like these should be in a module.
> People are arguing that ORMs are only leaky abstraction, and trying to > build the perfect one will result at reinventing SQL itself. Which is > not false imho. You can easily build generic methods to fetch object. > good idea. In PHP I developed a generic model class and then had individual table classes which inherited the base model class - the classes handled basic CRUD. I think this same idea would be good in webpy - adds a good "model" structure without all the overhead of an ORM. This would be a good "webpy cookbook" addition. in many ways, webpy reminds me of the PHP framework "CodeIgniter" which has a separate model module but does not rely on it (and I never used it). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
