db.Field or SQLField??

[Italo Maia]

Just saw a video (http://www.vimeo.com/2720410) where db.Field was
user, and not SQLField...Which should be used?

[mdipierro]

db.Field() because it avoid conflicts when running on Google App
Engine.

[desfrenes]

I'm not sure to understand what that means... you mean SQLField should
be used in relational databases and Field in non-relational
databases ?

[mdipierro]

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

[desfrenes]

ok, this is clear now :-)

[Italo Maia]

shouldn't SQLField be removed, then?

[Italo Maia]

The shortcut, i mean.

On 16 abr, 10:07, desfrenes <desfre...@gmail.com> wrote:

[Iceberg]

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.

[mdipierro]

There is also the issue of form_factory. You have no DB there and must
use SQLField.

Massimo

[Yannick]

Good to know... Those can be good subject in the new version of the
book since it can be confusing for new user... I didn't know that b4.

Thanks for the thread,
Yannick P.