> (record, row, column) should be atomic -- represent only one thing,
I think that�s the problem he has noticed.
Tim, Yes, your analysis is correct. You will have MANY problems with it this
way, and Yes, you can use the auto-incrementing ID to make your unique keys
Dick is right; you don�t want to just dump the structure straight into the
DB. You are going to have to step through it and enter data one row at a
time. Let�s see that structure and we�ll work it out from there.
_____
From: Dick Applebaum [mailto:[EMAIL PROTECTED]
Sent: Friday, September 10, 2004 8:32 AM
To: CF-Talk
Subject: Re: inserting structure data into a database
Tim
One of the basic rules of good relational db design is that each entity
(record, row, column) should be atomic -- represent only one thing,
You should not insert a structure into a db
Rather, insert each cassette as a separate row (record) in the db
If there is a relationship among the multiple cassettes that you
currently have in the structure, consider adding an identifier (group)
to each record in the db.
ID
Title
IssueNumber
IssueDate
Group
Dick
On Sep 10, 2004, at 5:23 AM, Tim Laureska wrote:
> Just learning structures, but here goes:
>
> When I insert structure data into a database, it's inserted into each
> field as a comma delimited list.
>
> In this scenario, I'm inserting audio cassette tape information into
> the
> database from a form when multiple cassettes are entered at one time.
> There are three attributes to for each cassette... title, issue date
> and
> issue number, which are the fields in the database (along with an
> autoid
> field).
>
> So if three cassettes are entered and subsequently inserted into the
> database, the data goes in as such:
>
> Auto id title field issue number field issue date
> field
>
> 1 title1, title2, title3 issue1,issue2,issue3
> date1,date2,date3
>
> This seems to present a problem in that each cassette does not have a
> unique autoid to identify it individually and that may present issues
> further in the application...
>
> My questions are: 1) is this analysis correct and 2)how can you
> maintain a unique id for each cassette in this situation ... do you
> have
> to assign a unique number for each cassette using some sort of CF code
> or is there a way to still utilize the DB's automatic unique id
> assignment feature?
_____
[HYPERLINK "http://www.houseoffusion.com/lists.cfm/link=t:4"Todays Threads]
[HYPERLINK "http://www.houseoffusion.com/lists.cfm/link=i:4:177849"This
Message] [HYPERLINK
"http://www.houseoffusion.com/lists.cfm/link=s:4"Subscription] [HYPERLINK
"http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=678.598.4"Fast
Unsubscribe] [HYPERLINK "http://www.houseoffusion.com/signin/"User Settings]
[HYPERLINK
"https://www.paypal.com/cgi-bin/webscr?amount=&item_name=House+of+Fusion&bus
iness=donations%40houseoffusion.com&undefined_quantity=&cmd=_xclick"Donation
s and Support]
_____
HYPERLINK "http://www.houseoffusion.com/banners/view.cfm?bannerid=36" \n
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.759 / Virus Database: 508 - Release Date: 9/9/2004
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.759 / Virus Database: 508 - Release Date: 9/9/2004
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
