fbsd_user wrote:
Thank you Gabriel, more background information may result in a
better concept, so here it is.
The web based application I am writing deals with people who have an
a home for rent. They can sign up for small fee and enter their
rental property into the application so its searcha
> My current thinking is to break the entering of the property
> info into 3 separate forms, the first with the mandatory info
> does a insert to create the row with the remaining 100
> columns being seeded with $t=''. Group 2 & 3 will them be a
> update to the row using the 'set' keyword just touc
s under their separate
> control.
>
>
> Does this sound like a workable solution or is there some other
> approach that is better suited to my application?
>
> Thanks to all the people who have replied all ready.
>
>
>
> -Original Message-
> From: Gab
PROTECTED]
Sent: Tuesday, March 14, 2006 6:39 PM
To: Mysql
Subject: Re: Very large from
At 4:24 pm -0500 14/3/06, fbsd_user wrote:
>user has to use the power bar to move deeper into the form
Out of curiosity, what's "the power bar"?
>From a db perspective one single insert is pre
olution or is there some other
approach that is better suited to my application?
Thanks to all the people who have replied all ready.
-Original Message-
From: Gabriel PREDA [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 15, 2006 5:01 AM
To: Mysql
Subject: Re: Very large from
Hm
You could also use a temp table, put data into it page-by-page and
insert the complete row after a last check into the "real" table.
This temp table might have an additional timestamp field according to
which evth. older than 1h(or some other time period) could easily be
deleted by a cronjob.
Hmmm...
Let me say some thoughts...
First *fbsd_user* said that he has *100 input fields plus 40 different drop
downs.*
And everybody is arguing that they prefer "*one single insert*".
Is it just me... or are you thinking at a table with 140 columns ?
Thinking at such a monster... all the above di
At 4:24 pm -0500 14/3/06, fbsd_user wrote:
>user has to use the power bar to move deeper into the form
Out of curiosity, what's "the power bar"?
>From a db perspective one single insert is preferable, IMO. Firstly you don't
>have to declare as NULL required fields that will be entered in the sec
l.com
Subject: Re: Very large from
Not wanting to be rude but this question would probably be answered
better in a php group. I realise there are many users of php that
subscribe to this list, but this is a mysql list not php.
If you go to http://www.php.net/support.php you will find a large
numb
-Original Message-
From: Brett Harvey [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 14, 2006 4:35 PM
To: [EMAIL PROTECTED]; mysql@lists.mysql.com
Subject: Re: Very large from
Both methods are "commonly" used.
Another method used is to have multiple pages like you've mentioned
but
On Tuesday 14 March 2006 22:24, fbsd_user wrote:
> Have to develop form with over 100 input fields plus 40 different
> drop downs. Seeking advice on technique to use. Thinking about
> single form where user has to use the power bar to move deeper into
> the form. This has benefit that every thing i
Not wanting to be rude but this question would probably be answered
better in a php group. I realise there are many users of php that
subscribe to this list, but this is a mysql list not php.
If you go to http://www.php.net/support.php you will find a large number
of resources (including lists
Both methods are "commonly" used.
Another method used is to have multiple pages like you've mentioned
but save all the data into a session (of just pass it from page to
page) until all 3 pages are complete and then write all the data at
once
The question to ask yourself is, do you want just
Have to develop form with over 100 input fields plus 40 different
drop downs. Seeking advice on technique to use. Thinking about
single form where user has to use the power bar to move deeper into
the form. This has benefit that every thing is written to the
database at one time, but the draw back
14 matches
Mail list logo
