I suppose it depends on what you mean by this " application logic completely independent from persistent data storage" So you certainly can have that completely independent, though you wouldn't persist anything. Is the idea that you'd update a memory representation of objects only, and somehow your data will be automatically persisted? If so, you can certainly program it that way as well.
Often times we'll get people here asking about something they read in a book somewhere about how this would be better and why doesn't Web2py support this something. Chances are, web2py does support this something, but not everyone is in agreement that this something is better. Time and experience are the greatest teachers. As for you, I'd suggest that if you can provide us with concrete examples of where a 'data mapper' is what you need, and why you choose this, perhaps we can review the capabilities of web2py with you. On Sunday, December 14, 2014 12:54:42 PM UTC-7, Alan Evangelista wrote: > > Simple is a relative term, I should not have associated it with web2py > DAL. What I meant is that I want to make my application logic completely > independent from persistent data storage. The only method I know to > implement this is using the data mapper design pattern ( > http://en.wikipedia.org/wiki/Data_mapper_pattern). It seems to me this is > impossible using only web2py DAL, I'd have to implement an ORM on top of > web2py DAL. Is that correct? If not, please provide details on how I would > achieve this. > > Thanks in advance! > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
