Override data/update SQLFORM behavior - web2py-users

9 messages - Collapse all

Gary

View profile

More options Apr 26, 7:37 pm

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

  Reply to author
  |
  Forward
  | Print
  | Individual message
  | Show original
  | Report this message
  | Find messages by this author
  

Is there a simple way to replace the automatically generated SQLFORM
in the various crud controllers with a custom SQLFORM?

Thanks.

Reply to author Forward

mdipierro

View profile

More options Apr 26, 9:22 pm

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

Date: Sun, 26 Apr 2009 18:22:40 -0700 (PDT)

Local: Sun, Apr 26 2009 9:22 pm

Subject: Re: Override data/update SQLFORM behavior

  Reply to author
  |
  Forward
  | Print
  | Individual message
  | Show original
  | Report this message
  | Find messages by this author
  

Yes, you can make the form in html as usual for SQLFORM.

On 26 Apr, 18:37, Gary <gary.k.ma...@gmail.com> wrote:

- Show quoted text -

Reply to author Forward

Gary

View profile

More options Apr 27, 4:14 pm

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

Date: Mon, 27 Apr 2009 13:14:16 -0700 (PDT)

Local: Mon, Apr 27 2009 4:14 pm

Subject: Re: Override data/update SQLFORM behavior

  Reply to author
  |
  Forward
  | Print
  | Individual message
  | Show original
  | Report this message
  | Find messages by this author
  

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

On Apr 26, 9:22 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:

- Show quoted text -

Reply to author Forward

mdipierro

View profile

More options Apr 27, 5:48 pm

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

  Reply to author
  |
  Forward
  | Print
  | Individual message
  | Show original
  | Report this message
  | Find messages by this author
  

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())

- Show quoted text -

Reply to author Forward

Gary

View profile

More options Apr 27, 6:23 pm

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

  Reply to author
  |
  Forward
  | Print
  | Individual message
  | Show original
  | Report this message
  | Find messages by this author
  

Massimo,

Thank you, Thank you, Thank you! This clarified so much and makes a
great deal of sense.

Kindest regards,
Gary

On Apr 27, 5:48 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:

- Show quoted text -

Reply to author Forward

mdipierro

View profile

More options Apr 27, 6:31 pm

From: 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

  Reply to author
  |
  Forward
  | Print
  | Individual message
  | Show original
  | Report this message
  | Find messages by this author
  

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

Massimo

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

- Show quoted text -

> Massimo,

> Thank you, Thank you, Thank you! This clarified so much and makes a
> great deal of sense.

> Kindest regards,
> Gary

> On Apr 27, 5:48 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:

> > 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())

> > > 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

> > > On Apr 26, 9:22 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:

> > > > Yes, you can make the form in html as usual for SQLFORM.

> > > > On 26 Apr, 18:37, Gary <gary.k.ma...@gmail.com> wrote:

> > > > > Is there a simple way to replace the automatically generated SQLFORM
> > > > > in the various crud controllers with a custom SQLFORM?

> > > > > Thanks.

Reply to author Forward

Gary

View profile

More options Apr 27, 7:44 pm

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

  Reply to author
  |
  Forward
  | Print
  | Individual message
  | Show original
  | Report this message
  | Find messages by this author
  

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

On Apr 27, 6:31 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:

- Show quoted text -

> 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

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

> > Massimo,

> > Thank you, Thank you, Thank you! This clarified so much and makes a
> > great deal of sense.

> > Kindest regards,
> > Gary

> > On Apr 27, 5:48 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:

> > > 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())

> > > > 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

> > > > On Apr 26, 9:22 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:

> > > > > Yes, you can make the form in html as usual for SQLFORM.

> > > > > On 26 Apr, 18:37, Gary <gary.k.ma...@gmail.com> wrote:

> > > > > > Is there a simple way to replace the automatically generated SQLFORM
> > > > > > in the various crud controllers with a custom SQLFORM?

> > > > > > Thanks.

Reply to author Forward

Álvaro Justen [ Turicas ]

View profile

More options Apr 27, 8:15 pm

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

  Reply to author
  |
  Forward
  | Print
  | Individual message
  | Show original
  | Report this message
  | Find messages by this author
  

.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/

Reply to author Forward

Gary

View profile

More options Apr 29, 8:52 am

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

Date: Wed, 29 Apr 2009 05:52:01 -0700 (PDT)

Local: Wed, Apr 29 2009 8:52 am

Subject: Re: Override data/update SQLFORM behavior

  Reply to author
  |
  Forward
  | Print
  | Individual message
  | Show original
  | Report this message
  | Find messages by this author
  

Sorry for being so long winded.
I've been trying to implement a custom html form using the crud
applications as explained above, but I'm having difficulty using
custom html. Here is the test MVC that I've created for the purpose
of understanding the concepts:

Model
--------
try:
from gluon.contrib.gql import * # if running on Google App Engine
except:
db = SQLDB('sqlite://storage.db') # if not, use SQLite or other
DB
else:
db = GQLDB() # connect to Google BigTable
session.connect(request, response, db=db) # and store sessions
there
##
db.define_table('testtable',SQLField('testfield1','string'),SQLField
('testfield2','string'))

from gluon.tools import Mail, Auth, Crud # new in web2py 1.56
crud=Crud(globals(),db) # for CRUD helpers using
auth
crud.settings.update_next = URL(r=request, f='index')
=====

Controller
------------
def index():
redirect(URL(r=request,f='testupdate',args=["1"]))

def testupdate():
id=request.args[0]
return dict(form=crud.update(db.testtable,id))

def data():
response.view="%s/%s/%s.html" %
(request.controller,request.function, request.args[0])
return dict(form=crud())

=======

View (default/testupdate.html)

{{extend 'layout.html'}}
<h1>This is the default/testupdate.html template</h1>

{{=form}}

{{for field in form:}}
{{=field}}
{{pass}}

<table>
<tr id="testtable_testfield1__row">
<td><label for="testtable_testfield1"
id="testtable_testfield1__label">Testfield1: </label></td>
<td><input class="string" id="testtable_testfield1"
name="testfield1" type="text" value="testdata1" /></td>
<td></td>
</tr>
<tr id="testtable_testfield2__row">
<td><label for="testtable_testfield2"
id="testtable_testfield2__label">Testfield2: </label></td>
<td><input class="string" id="testtable_testfield2"
name="testfield2" type="text" value="testdata2" /></td>
<td></td>
</tr>
<tr id="delete_record__row">
<td><label for="delete_record" id="delete_record__label">Check to
delete:</label></td>
<td><input class="delete" id="delete_record"
name="delete_this_record" type="checkbox" value="on" /></td>
<td></td></tr><tr id="submit_record__row"><td></td><td><input
type="submit" value="Submit" /></td>
<td></td>
</tr>
</table>
<div class="hidden"><input name="_next" type="hidden" value="http://
localhost:8001/test/default/testupdate/1" />
<input name="id" type="hidden" value="1" />
<input name="_formkey" type="hidden" value="b7418550-1b4a-434b-
bdc1-84a24e904582" />
<input name="_formname" type="hidden" value="testtable_1" />
</div>
</form>

========

It's obvious that the hidden field 'formname' is required and changes
with each submission. I assume that there is a value that can be
inserted there to fix that problem, but is this the best/only way to
gain full control of the display of a crud application? Any insight
will be greatly appreciated.

Thanks,
Gary

====================================================================
====================================================================

On Apr 27, 6:31 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:

- Show quoted text -

> 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

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

> > Massimo,

> > Thank you, Thank you, Thank you! This clarified so much and makes a
> > great deal of sense.

> > Kindest regards,
> > Gary

> > On Apr 27, 5:48 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:

> > > 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())

> > > > Thank you.
> > > > Gary

> > > > On Apr 26, 9:22 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:

> > > > > Yes, you can make the form in html as usual for SQLFORM.

> > > > > On 26 Apr, 18:37, Gary <gary.k.ma...@gmail.com> wrote:

> > > > > > Is there a simple way to replace the automatically generated SQLFORM
> > > > > > in the various crud controllers with a custom SQLFORM?

> > > > > > Thanks.

Reply to author Forward

End of messages

« Back to Discussions

« Newer topic

Older topic »