Howard" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Friday, January 17, 2003 11:39 AM
Subject: RE: Best way to store 40 values?
> Ah, what the hell ... I'll weigh ... besides ... I've done this -- this
> exact thing.
>
> I assume wi
Ah, what the hell ... I'll weigh ... besides ... I've done this -- this
exact thing.
I assume with 10,000 songs to choose from, what you want to create is some
sort of shopping cart.
Users will want to browse by Artist, Song Title, Song Style, at least.
Users will also want to be able to search
On Friday 17 Jan 2003 15:27 pm, Robertson-Ravo, Neil (RX) wrote:
> uurgh, I support its Fri and I can have a beer!
I blame it on *already* having had beer :-)
Besides, all my posts to the list seemed to have been silently binned (though
they made it to the web archive) till today, when I got a
On Friday 17 Jan 2003 15:26 pm, Jochem van Dieten wrote:
> No, ID's are required to be unique, names are not. It is explicitly in
> the standard: http://www.w3.org/TR/html4/interact/forms.html#h-17.2.1
Fair 'nough :-)
--
Tom C
'Man's greatest joy is to slay his enemy, plunder his riches,
ride
You are correct, sorry Jochem..i was getting confused with Radio buttons...
uurgh, I support its Fri and I can have a beer!
-Original Message-
From: Jochem van Dieten [mailto:[EMAIL PROTECTED]]
Sent: 17 January 2003 15:26
To: CF-Talk
Subject: Re: Best way to store 40 values?
Thomas
>it'll certainly confuse the hell out of fusebox.
Huh? You'll ultimately regret storing it as a string rather using the
DB as intended, but Fusebox won't have any more trouble with it than a
non-Fusebox app.
Ken
~|
Archives: ht
n-Ravo, Neil (RX)
> [mailto:[EMAIL PROTECTED]]
> Sent: Friday, January 17, 2003 10:12 AM
> To: CF-Talk
> Subject: RE: Best way to store 40 values?
>
>
> it will only return a list if its a multi selectbox I am sure.
>
> -Original Message-
> From: Thoma
Thomas Chiverton wrote:
> On Friday 17 Jan 2003 15:14 pm, Jochem van Dieten wrote:
>
>>>IANW3C but I think that that behaviour is 'undefined'.
>>
>>http://www.w3.org/TR/html4/interact/forms.html#h-17.13.3
>
>
> :peers
> Seems name should be unique.
No, ID's are required to be unique, names are
We also tend to leave out the ID field and just use (UserID, SongID) as the
primary key. When these are the only fields in the table, you're not
losing anything by using a hybrid key and you're saving a lot of space with
so many records.
4,000,000 records isn't really all that many for a table
Robertson-Ravo, Neil (RX) wrote:
> it will only return a list if its a multi selectbox I am sure.
The original example () is
a bit bad for 2 reasons:
- it is inappropriate to store the info as a list in the database
- the lack of proper formatting makes it confusing
However, the example does wor
On Friday 17 Jan 2003 15:14 pm, Jochem van Dieten wrote:
> > IANW3C but I think that that behaviour is 'undefined'.
>
> http://www.w3.org/TR/html4/interact/forms.html#h-17.13.3
:peers
Seems name should be unique.
--
Tom C
'All Bibles are man-made.'
- Thomas Edison
~~
it will only return a list if its a multi selectbox I am sure.
-Original Message-
From: Thomas Chiverton [mailto:[EMAIL PROTECTED]]
Sent: 17 January 2003 15:06
To: CF-Talk
Subject: Re: Best way to store 40 values?
On Friday 17 Jan 2003 14:43 pm, Scott Wilhelm wrote:
> )...Then, when
Thomas Chiverton wrote:
> On Friday 17 Jan 2003 14:43 pm, Scott Wilhelm wrote:
>
>>)...Then, when you process
>>the results of the form, the value for songid will come back as
>>1,2,3,4,5,6,7,8,9...just store it as that...
>
>
> IANW3C but I think that that behaviour is 'undefined'.
http://www.
On Friday 17 Jan 2003 15:04 pm, Robertson-Ravo, Neil (RX) wrote:
> eh?
Oh ?
--
Tom C
Hey baby, I'm a particle and you're a quantum potential.. can I penetrate your
classically forbidden region?
~|
Archives: http://www.houseof
Paul Giesenhagen wrote:
> You could create a database like this:
>
> ID|USERID|SONGID
> 11222
> 21443
> 319494
> 42999
> 52443 etc...
Leave out the ID field and use a composite primary key on both userid
and songid.
eh?
-Original Message-
From: Thomas Chiverton [mailto:[EMAIL PROTECTED]]
Sent: 17 January 2003 15:06
To: CF-Talk
Subject: Re: Best way to store 40 values?
On Friday 17 Jan 2003 14:43 pm, Scott Wilhelm wrote:
> )...Then, when you process
> the results of the form, the value for
On Friday 17 Jan 2003 14:43 pm, Scott Wilhelm wrote:
> )...Then, when you process
> the results of the form, the value for songid will come back as
> 1,2,3,4,5,6,7,8,9...just store it as that...
IANW3C but I think that that behaviour is 'undefined'. I'm fairly sure
NS/Mozilla will only return one
How about we not break the most basic rules of normalization for no good
reason. Both XML and list methodologies are lumping separate data elements
together into a single field.
If you do this you're going to have lots of problems down the road. With a
list or xml, how can you determine the a
Friday, January 17, 2003 8:49 AM
Subject: Re: Best way to store 40 values?
> If the songs all have a unique ID, why not just store the ID's as a comma
> separated list in one field?
> - Original Message -
> From: "Paul Campano" <[EMAIL PROTECTED]>
> To: &q
indexing you should be fine.
Paul Giesenhagen
QuillDesign
- Original Message -
From: "Paul Campano" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Friday, January 17, 2003 8:51 AM
Subject: Best way to store 40 values?
> I have a database of a
Why not just use a delimited list? Or save it in the database as WDDX or
XML?
- Original Message -
From: "Paul Campano" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Friday, January 17, 2003 9:51 AM
Subject: Best way to store 40 values?
>
If the songs all have a unique ID, why not just store the ID's as a comma
separated list in one field?
- Original Message -
From: "Paul Campano" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Friday, January 17, 2003 8:51 AM
Subject: Best
l Campano [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 17, 2003 9:52 AM
To: CF-Talk
Subject: Best way to store 40 values?
I have a database of approx 1 songs. I want users to be able to
choose 40 of them (probably using checkboxes via a form) and save their
preference of these songs to a da
you want to find out what they selected, just have it split
the value by the comma, and put that into an array...Then go that
route...
HTH!
Scott
-Original Message-
From: Paul Campano [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 17, 2003 9:52 AM
To: CF-Talk
Subject: Best way to stor
to store 40 values?
I have a database of approx 1 songs. I want users to be able to choose
40 of them (probably using checkboxes via a form) and save their preference
of these songs to a database. I guess I could always make 40 database
fields named song1, song2, song3, but I figured
EMAIL PROTECTED]
WWW : www.camdenfamily.com/morpheus
Yahoo IM : morpheus
"My ally is the Force, and a powerful ally it is." - Yoda
> -Original Message-
> From: Paul Campano [mailto:[EMAIL PROTECTED]]
> Sent: Friday, January 17, 2003 8:52 AM
> To: CF-Talk
>
I have a database of approx 1 songs. I want users to be able to choose 40 of them
(probably using checkboxes via a form) and save their preference of these songs to a
database. I guess I could always make 40 database fields named song1, song2,
song3, but I figured there must be a bette
27 matches
Mail list logo
