The main advantage of the new dal is the ability to easily add adaptors for new backends and map virtual fieldnames into actual fieldnames. This does not mean you will be able to access legacy databases that you cannot access today. In fact the only and main issue is with fields that lack autoincrement it and references that do not use this field. This "limitation" (same for Django and Rails) is not going away because it is part of "enforcing good practice" and because bypassing it does not break the DAL but would break everything else from form processing to validators.
Massimo On Aug 10, 9:20 am, DenesL <denes1...@yahoo.ca> wrote: > On Aug 10, 4:17 am, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > I will release the book before the new DAL but the new DAL will be > > backward compatible. The only differences will be inside. The new DAL > > is taking longer then expected and I apologize but there is not really > > much pressure to get it done. > > I beg to differ on the urgency of the new DAL. > For one, being able to access databases not built with web2py would be > a huge boost for it. > > Denes. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
