a, i c, i've already re read the book that it seems that the SQLFORM parameter is same like on the parameter in DAL model, can it be collide? which one is use DAL model or SQLFORM? e.g. i set in DAL model : writable = False and in SQLFORM : readonly = False
Thank you On Mon, May 23, 2011 at 8:19 AM, Massimo Di Pierro < [email protected]> wrote: > a *lot of* overlap. > > On May 22, 8:08 pm, Stifan Kristi <[email protected]> > wrote: > > log overlap? is it for CRUD? i've already checked in web2py.com/bookthat > > the log is related with crud.message? please correct me if i'm wrong. > > thank you > > > > On Mon, May 23, 2011 at 7:53 AM, Massimo Di Pierro < > > > > > > > > > > > > > > > > [email protected]> wrote: > > > Use crud for fast prototyping. Use SQLFORM when you need more control. > > > The good thing is that they have a log overlap and you can always > > > change one for the other. > > > > > On May 22, 7:50 pm, Stifan Kristi <[email protected]> > > > wrote: > > > > same for me, still confuse about exact comparation between SQLFORM > and > > > CRUD, > > > > plus and minus side overview, but i usually use CRUD, because it's > simple > > > > (just my opinion). > > > > > > On Mon, May 23, 2011 at 7:39 AM, Ismael Alejandro < > > > [email protected]>wrote: > > > > > > > Hi apple! I'm my own experience (may me I'm wrong) I use SQLFORM > when I > > > > > need to customize a little the form, or when I have to deal with an > > > specific > > > > > var. > > > > > > > But, is a good question, same doubt here :s > > > > > > > On Sat, May 21, 2011 at 1:35 PM, apple <[email protected]> wrote: > > > > > > >> Can you do everything using CRUD that you can do with SQLFORM? > > > > > > >> Under what circumstances would you choose SQLFORM rather than > CRUD?
