On Friday 24 February 2006 10:56, Jason F. McBrayer wrote:
> Andrew Gwozdziewycz <[EMAIL PROTECTED]> writes:
> > Why not just store the values in the database after each pages
> > submission?
>
> That's a point. I hadn't observed that it was a multi-page form for
> creating an object --- I was lo
Andrew Gwozdziewycz <[EMAIL PROTECTED]> writes:
> Why not just store the values in the database after each pages
> submission?
That's a point. I hadn't observed that it was a multi-page form for
creating an object --- I was looking at the general case of multi-page
actions where you are not ne
On Feb 23, 2006, at 8:12 AM, Jason F. McBrayer wrote:
>
> "Chetan Vaity" <[EMAIL PROTECTED]> writes:
>
>> I want to build a two-page form for creating an object. As I see
>> it there are two options:
>> 1. Store values in hidden fields
>> 2. Use the session to store the variables from the firs
"Chetan Vaity" <[EMAIL PROTECTED]> writes:
> I want to build a two-page form for creating an object. As I see it there are
> two options:
> 1. Store values in hidden fields
> 2. Use the session to store the variables from the first form
>
> Any Django best practices?
I'd say use the session to
Hi,I want to build a two-page form for creating an object. As I see it there are two options:1. Store values in hidden fields2. Use the session to store the variables from the first formAny Django best practices?
- Chetan
--~--~-~--~~~---~--~~
You received this mess
5 matches
Mail list logo