I guess the answer is NO, because we need backward compatibility.
However, I would suggest to add the description about SQLField VS
db.Field in DAL document (http://www.web2py.com/examples/default/dal),
so old users do get confused when seeing db.Field at the first time. I
bet few people know the difference between SQLField and db.Field
before this discussing thread. I didn't know that too.

On Apr17, 6:00am, Italo Maia <italo.m...@gmail.com> wrote:
> shouldn't SQLField be removed, then?
>
> On 16 abr, 10:07, desfrenes <desfre...@gmail.com> wrote:
>
> > ok, this is clear now :-)
>
> > On Apr 16, 3:03 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> > > I am saying they are equivalent since db.Field == SQLField.
>
> > > Some times, if you use GAE, SQLField can be ambiguous (because there
> > > are two of them one in gluon.sql and one in gluon.contrib.gql).
> > > db.Field always refer to the correct one and avoids the ambiguity.
>
> > > I would suggest always using db.Field but this is not a big deal.
>
> > > Massimo
>
> > > On Apr 16, 5:12 am, desfrenes <desfre...@gmail.com> wrote:
>
> > > > I'm not sure to understand what that means... you mean SQLField should
> > > > be used in relational databases and Field in non-relational
> > > > databases ?
>
> > > > On Apr 16, 6:54 am, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> > > > > db.Field() because it avoid conflicts when running on Google App
> > > > > Engine.
>
> > > > > On Apr 15, 10:37 pm, Italo Maia <italo.m...@gmail.com> wrote:
>
> > > > > > Just saw a video (http://www.vimeo.com/2720410) where db.Field was
> > > > > > user, and not SQLField...Which should be used?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"web2py Web Framework" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to 
web2py+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to