Yes, it will be backward compatible unless you used internal and undocumented features of the DAL (like importing SQLSet or subclassing SQLRows). it will also expose a new alternative cleaner syntax (for example you will be asked to use Field instead of SQLField but SQLField works too as alias of Field).
I will explain more when done. Massimo On May 29, 8:29 pm, cesmiga <cesm...@gmail.com> wrote: > Massimo, > > Will the new DAL be backwards compatible with the existing DAL? The > reason I ask is because I have been using "WWW SQL Designer" and hope > to continue using it with the new DAL. > > Thank you, > Christopher > > mdipierro wrote: > > I am finishing a rewrite of the new DAL. It may be done in one week or > > two but I could use some help. > > I can explain exactly what to do. I need people to write and run tests > > for the supported backends. > > > It will be beackward compatible and have some new features including > > dealing with tables that do not have the 'id' field, realnames > > different than virtualnames for tables and columns, a certain degree > > of fail safety when multiple databases present, and be very modular > > and extensible (to add new engines and new fields and add methods to > > handle the fields values). It is also be smaller and I think faster > > than the old one. > > > Yes, this is possible and already have it working for sqlite. > > > Let me know if you can help. I need a serious commitment and proven > > expertise on this list. > > > Massimo > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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 -~----------~----~----~----~------~----~------~--~---
