Re: [web2py] Setting DAL less strict from a model

I just tested it with Michele's proposed code: Created a 0_db.py with the following content: real_DAL = DAL def DAL(*args, **kwargs): kwargs['check_reserved'] = False kwargs['entity_quoting'] = True return real_DAL(*args, **kwargs) Cool: the https://github.com/acidjunk/web2py-pages is n

Re: [web2py] Setting DAL less strict from a model

Hi, Just checked with trunk Version 2.8.2-stable+timestamp.2014.01.30.08.43.19 and entity_quoting=True in the DAL connection string; Then it works. (but I still have to remove the check_reserved from the DB connection URI) I really would like to build/release a .w2p/plugin that doesn't overwri

Re: [web2py] Setting DAL less strict from a model

Hi Mic, I will test it later on. But i'm not sure how this would solve the problem; I still need to remove the check_reserved from the DAL connection string. The goal is to NOT change anything in db.py; so the page module can be used as a normal w2p plugin. Or are you saying check_reserved will

Re: [web2py] Setting DAL less strict from a model

Hi Rene, try testing with trunk, remove check_reserved and add the following to DAL parameters: DAL(., entity_quoting=True) after that you should have no conflict with reserved SQL words. You should be able to use any name, e.g. do things like define_table('table', Field('select'), Field('u

[web2py] Setting DAL less strict from a model

Hi Web2py-users, I have developed a CMS kind of system based on web2py. https://github.com/acidjunk/web2py-pages I actually want to provide a release as a w2p file on a regular basis, so it can be used more easily. But I'm running into a problem if I don't overwrite any core web2py app files.