Usually people check the ``request.method`` and see if it's "POST" or
"GET", combined with making sure your forms submit using POST.
I.e. in pseudo-code:
if POST:
process form
maybe redirect to view
render form
\malthe
On 27 July 2011 22:02, Eduardo Miguez <[email protected]> wrote:
> Hi guys, I'm new to this Pyramid world (as a matter of fact I'm new to
> web development world) so I have a "best practice" question:
> Let's say I have this "users" model where I can store and retrieve
> user information such as name, social security id, address and the
> likes.
> If I want somebody to edit some of this information for a particular
> user I have to query the database and present the information through
> a view. If somebody updates some of that information it seems i have
> to create another view to receive the data, get the updated user id
> from the request, query the db again to populate an ORM object where
> to apply the changes submitted and update the instance. Looks to me
> that for every action I need to write two views and perform the same
> query twice (I would imagine that I could send the user instance in
> the view but I don't know how). Is that right?
>
> Thanks for any pointer!
>
> --
> You received this message because you are subscribed to the Google Groups
> "pylons-discuss" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/pylons-discuss?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en.
