both trunk and the nightly built in the web2py download page use the new dal as opposed to the old one. Please give it a try. Specifically if you are using something other than sqlite. please report any test you make. It is critical to know if this works fine because I am planning to remove completely the old dal as soon as possible.
Massimo On Dec 6, 6:08 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > For now, for testing purposes I am going to copy dal.py over sql.py > and post a nightly build using the new dal. > > Long term, is this ia good solution. I would like to keep both sql.py > and dal.py and import DAL, Field from the latter but this would break > existing "from gluon.sql import *". In order not to break it, the > current approach is the only approach (replace the old dal with the > new dal and call it sql.py). > > Any opinion on this matter? > > Massimo > > On Dec 6, 4:38 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > With the new DAL it should take very little to create a DAL interface > > to mongodb, couchdb, etc. > > > I can work on this if > > - you help me prioritize > > - you can give me access to a machine that already has your favorite > > nosql db installed ready for testing > > > Massimo > > > On Dec 6, 3:10 pm, Jonathan Lundell <jlund...@pobox.com> wrote: > > > > On Dec 6, 2010, at 12:55 PM, mdipierro wrote: > > > > > 1) The new DAL (dal.py) passes all the tests I have. > > > > 2) The new DAL has integrated GAE support (datastore) without need for > > > > contrib/gql.py > > > > 3) The new DAL is better because more customizable, smaller (10%), and > > > > more readable > > > > 4) The new DAL is one single file and it does not depend on web2py. > > > > Have you decided to keep it as a single file, or break it into a package? > >
