> > Why not? That's how ORMs do it -- everything related to a given model > lives in a single class. After all, the logic in question does pertain to > the associated model. >
You don't need classes to organize code. > All the tables/models are connected somehow by reference fields. I dont know how to define a table without defining the ones that its referencing, even if im not going to use them. Thats why im defining all the tables just in case i want to access a reference field from an undefined table. Its often the case that im using a field which reference is 2, 3 or more tables away. So i define all the tables but load only the models/classes im using for that controller. This way i also separate the controllers logic, which is basically the request's handler (define requeriments for the view), and the models (business logic). > If you must have an ORM, you might try the weppy ORM (built on top of the > web2py DAL), or just switch to SQLAlchemy. > I really like DAL, actually i like everything about web2py, the more i learn the more i like it (besides the scheduler, leave that one out.) Ive read about SQLAlchemy and it isnt that easy to use. From the time being all web2py features are more than enough to achieve what im working in. I didnt know about webppy but i dont think i will learn it, since as i said im happy with DAL for now. Ill have in mind your words since im reorganizing my project right now, all your suggestion are welcome. Thanks. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
