Where do you see the reference to web2py in the document. I did not see it.
web2py allows for keyed tables (not on all supported database) and a key can be uuid. yes forms will not work well with it (at least I never tried) and web2py was designed with an integer ID in mind. This is not a fundamental design issue but more of a constraint that is imposed in various parts of the code. For example db.table[x] if x is integer assumes you want a record with id==x and if x is a string, it assumes you want the field object with that name. In retrospect assuming id was integer was a mistake (we copied Django and we should not have) and this is the main obstacle to port web2py DAL API on top of NoSQL databases. Eventually this constraint will be relaxed. Massimo On Sep 9, 4:07 pm, johntynan <jgty...@gmail.com> wrote: > Nice mention of web2py about the application object. > > I've run into a snag with web2py by not knowing I should have have > UUID primary keys... Is this something that could be handled at the > web2py level and not within the app/model itself? Would this be > similar to what the author means by late binding FKs? > > On Sep 9, 1:13 pm, Adi <aditya.sa...@gmail.com> wrote: > > >http://www.scribd.com/doc/37113340/Why-Django-Sucks-and-How-we-Can-Fi... > > > It would be interesting to head community's thoughts on some of the > > problems there. :) > >
