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 overwrite
your existing db.py: or give a cryptic error on first time usage.
I hope it will be a default value in the next release or that there is some
simple way to set it with a function call in the future: entity_quoting and
check_reserved seem to be a DAL connection argument only.
Kind Regards
Rene
On Thursday, February 6, 2014 7:03:29 PM UTC+1, Rene Dohmen wrote:
>
> 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 be removed in the future; e.g. it
> wil be replaced by entity_quoting=True by default?
>
> Kind regards
> Rene
>
> On Tuesday, February 4, 2014 10:01:04 PM UTC+1, Michele Comitini wrote:
>>
>> 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('update'))
>>
>> Let us know if that works.
>>
>> mic
>>
>>
>>
>> 2014-02-04 Rene Dohmen <[email protected]>:
>>
>>> 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.
>>> https://github.com/acidjunk/web2py-pages/blob/master/README.md
>>>
>>> When I started the development (web2py 1.97.2) I made some DB naming
>>> choices that gave problems later on, when using strict(er) mode in DAL. The
>>> key problem is that we choose 'page' for our main table containing the
>>> pages. Obviously a lot of code in the page controller is using 'page' also
>>> for adding, editing and sorting pages; and I also have some projects in
>>> production that use it already. So a rename is not that straight forward or
>>> easy...
>>>
>>> I did investigate the web2py docs to see if I could relax the strict
>>> mode from a model that would be included after db.py; but that doesn't seem
>>> to be possible.
>>>
>>> Any help is appreciated.
>>>
>>> Kind Regards
>>>
>>> Rene
>>>
>>> --
>>> Resources:
>>> - http://web2py.com
>>> - http://web2py.com/book (Documentation)
>>> - http://github.com/web2py/web2py (Source code)
>>> - https://code.google.com/p/web2py/issues/list (Report Issues)
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "web2py-users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>
>>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
