Hi Thadeus,

I'm not doing any checking with "check_reserved" (http://web2py.com/
book/default/chapter/06?search=reserved#Reserved-Keywords), if that's
what you're asking.

I really did not fully understand that section, does it only check
whether the current table and field names are in conflict or not?.

I would still have to change the conflicting names, wouldn't I?.

Thanks,

   Carlos


On Dec 12, 5:55 pm, Thadeus Burgess <[email protected]> wrote:
> Are you using the reserved_keywords check built into the DAL?
>
> --
> Thadeus
>
>
>
>
>
>
>
> On Sun, Dec 12, 2010 at 2:50 PM, Carlos <[email protected]> wrote:
> > Hi Massimo,
>
> > Thanks for clarifying this.
>
> >   Carlos
>
> > On Dec 11, 7:41 pm, mdipierro <[email protected]> wrote:
> > > No. Right now there may problems if you used a reserved keyword.
>
> > > On Dec 11, 6:57 pm, Carlos <[email protected]> wrote:
>
> > > > Hi,
>
> > > > With respect to the following old thread:
>
> > > >http://groups.google.com/group/web2py/browse_thread/thread/6a0948e7bf.
> > ..
>
> > > > Is web2py now ready to use reserved words as table and field names
> > > > (e.g. "user", "group") without any conflicts with any of the supported
> > > > databases?.
>
> > > > Or what should be done in order to be "portable" across multiple
> > > > databases?.
>
> > > > Thanks,
>
> > > >    Carlos

Reply via email to