Serialize the struct using wddx, and insert the wddx package :-)
Micha Schopman
Software Engineer
Modern Media, Databankweg 12 M, 3821 ALAmersfoort
Tel 033-4535377, Fax 033-4535388
KvK Amersfoort 39081679, Rabo 39.48.05.380
[Todays Threads]
[This Message]
[Subscription]
[Fast
Does your structure, for some reason, look like this??
Title = title1,title2,title3
Issue = Issue1,issue2,issue3
IssueDate = date1,date2,date3
Lets see your structure/array code. Im sure Ive got a cfc around here
somewhere thatll fit your needs
_
From: Tim Laureska
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
I absolutely second this.
- Original Message -
From: Dick Applebaum
To: CF-Talk
Sent: Friday, September 10, 2004 8:32 AM
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
]
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
: 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
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
To follow-up on Dick's comments below.. that is my initial question ...
is a structure appropriate for the scenario I described or is there a
better way ... I see it as either use structures, but somehow break out
the data from the structure into separate rows-OR- use some other
method
You should
of a structure.
http://www.kodefusion.com/article/index.cfm?ArticleID=2
_
From: Tim Laureska [mailto:[EMAIL PROTECTED]
Sent: Friday, September 10, 2004 8:52 AM
To: CF-Talk
Subject: RE: inserting structure data into a database
body
Wow, that was a great array of responses ...the code
1) you could insert a record into the db as you build each structure
entry (cassette)
2) you could insert a record into the db as you display each structure
entry (cassette)
Does your input form allow multiple cassette entries on 1 form
submission?
If not, do you plan to store multiple form
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
, 2004 9:17 AM
To: CF-Talk
Subject: RE: inserting structure data into a database
One of the basic rules of good relational db design is that each
entity
(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
[mailto:[EMAIL PROTECTED]
Sent: Friday, September 10, 2004 8:58 AM
To: CF-Talk
Subject: Re: inserting structure data into a database
Yes!
What you should do is loop thru the multiple entries, and do a db
insert for each entry.
If you continue in the current direction (non-atomic) you will create
On Sep 10, 2004, at 6:37 AM, Tim Laureska wrote:
OK ... so much for a structure in this case ... now onto the challenge
of creating the loop coding you reference
I'm not sure where I was convinced to go the structure route... If I
may ask, what is a typical scenario when you DO use a
: Friday, September 10, 2004 10:14 AM
To: CF-Talk
Subject: Re: inserting structure data into a database
On Sep 10, 2004, at 6:37 AM, Tim Laureska wrote:
OK ... so much for a structure in this case ... now onto the challenge
of creating the loop coding you reference
I'm not sure where I
On Sep 10, 2004, at 7:33 AM, Tim Laureska wrote:
So, is this a reverse of what you were saying (don't use structures for
the scenario I was describing) in that I could use a structure and
break
it apart to insert data in individual rows using the code below ??
Tim
Not necessarily!
If you
: Dick Applebaum [mailto:[EMAIL PROTECTED]
Sent: Friday, September 10, 2004 10:48 AM
To: CF-Talk
Subject: Re: inserting structure data into a database
On Sep 10, 2004, at 7:33 AM, Tim Laureska wrote:
So, is this a reverse of what you were saying (don't use structures
for
the scenario I
17 matches
Mail list logo
