From
http://groups.google.com/group/web2py/browse_thread/thread/05c0b01480366044  

From: Gary <gary.k.ma...@gmail.com>
Date: Sun, 26 Apr 2009 16:37:03 -0700 (PDT)
Local: Sun, Apr 26 2009 7:37 pm
Subject: Override data/update SQLFORM behavior
Is there a simple way to replace the automatically generated SQLFORM
in the various crud controllers with a custom SQLFORM?

Thanks.

Like myapp/default/display_manual_form() in the book, right?

Two questions.   I assume that I need a:

def data(): return dict(form=crud())

for each table that uses the crud controller to properly define the

URL.   If that's true, it's the part that I missed.

Second, is it better to call the update directly like:

1) http://hostname/myapp/default/data/update/person/2

or create a controller like:

2) def update1():

      redirect(URL(r=request,f='data/update/person/2'))

In either case, what should the view be named?   Since one might want

to have a different view for read,update,delete,etc., it seems that it

should be:

default/data/update.html, but my testing seems to work at default/

data.html.

That seems to imply that using method #2 above with a response.view()

would be the better solution.   Would you agree with that conclusion or

is there a better way to handle this?

Thank you.

Gary

From: mdipierro <mdipie...@cs.depaul.edu>

Date: Mon, 27 Apr 2009 14:48:52 -0700 (PDT)

Local: Mon, Apr 27 2009 5:48 pm

Subject: Re: Override data/update SQLFORM behavior

On Apr 27, 3:14 pm, Gary <gary.k.ma...@gmail.com> wrote:

> Like myapp/default/display_manual_form() in the book, right?

> Two questions.   I assume that I need a:

> def data(): return dict(form=crud())

> for each table that uses the crud controller to properly define the

> URL.   If that's true, it's the part that I missed.

No. This controller will work for every table in the database. In

fact, as you do below, you specify the table in the URL

> 1)http://hostname/myapp/default/data/update/person/2

You create a CRUD action per table

def mycreate():

    return dict(form=crud.create(db.mytable))

or an update action

def myupdate():

    id=request.args[0]

    return dict(form=crud.update(db.mytable,id))

> or create a controller like:

> 2) def update1():

>        redirect(URL(r=request,f='data/update/person/2'))

  Do do not do actions that just redirect.

> In either case, what should the view be named?

  The view is the controller/action.html

> Since one might want

> to have a different view for read,update,delete,etc., it seems that it

> should be:

> default/data/update.html, but my testing seems to work at default/

> data.html.

  you can do

def data():

    response.view="%s/%s/%s.html"%(request.controller, request.function, request.args[0])

    return dict(form=crud())

From: Gary <gary.k.ma...@gmail.com>

Date: Mon, 27 Apr 2009 15:23:28 -0700 (PDT)

Local: Mon, Apr 27 2009 6:23 pm

Subject: Re: Override data/update SQLFORM behavior

Massimo,

Thank you, Thank you, Thank you!    This clarified so much and makes a

great deal of sense.

Kindest regards,

Gary

Fom: mdipierro <mdipie...@cs.depaul.edu>

Date: Mon, 27 Apr 2009 15:31:17 -0700 (PDT)

Local: Mon, Apr 27 2009 6:31 pm

Subject: Re: Override data/update SQLFORM behavior

when you call crud you can also specify lots of options...

def mycreate():

   return dict(form=crud.create(db.mytable,next=URL(...),onaccept=lambda form:pass,onvalidation=lambda form: pass))

and more. You can also embed them in views

   { {=crud.create(db.mytable)} }

Massimo

From: Gary <gary.k.ma...@gmail.com>

Date: Mon, 27 Apr 2009 16:44:28 -0700 (PDT)

Local: Mon, Apr 27 2009 7:44 pm

Subject: Re: Override data/update SQLFORM behavior

It's going to take some time to digest this, especially the

onxxx=lambda part.   When would you use the embedded form rather than

the controller/view combination above?   Are there any examples of the

either (or both) the these?   If not, once I understand this better,

I'd be happy to contribute to the documentation.

Thanks again,

Gary

From: Álvaro Justen [Turicas] <alvarojus...@gmail.com>

Date: Mon, 27 Apr 2009 21:15:08 -0300

Local: Mon, Apr 27 2009 8:15 pm

Subject: Re: [web2py:20692] Re: Override data/update SQLFORM behavior

.On Mon, Apr 27, 2009 at 8:44 PM, Gary <gary.k.ma...@gmail.com> wrote:

> It's going to take some time to digest this, especially the

> onxxx=lambda part.   When would you use the embedded form rather than

> the controller/view combination above?   Are there any examples of the

> either (or both) the these?   If not, once I understand this better,

> I'd be happy to contribute to the documentation.

  http://docs.python.org/tutorial/controlflow.html#lambda-forms

  Álvaro Justen

  Peta5 - Telecomunicações e Software Livre

  21 3021-6001 / 9898-0141

  http://www.peta5.com.br