Hi. I have a database table which currently has 21 fields - id and 20 fields which hold text links to the location of download items.
I've set up a series of "admin" pages for this table so that the user can create new records and update existing records - this works OK, but there's a small problem which I need some help with.
If the user were to make all 20 uploads in one go, that would be fine and all the data would be written into one row in the table. However, if he uploads (say) 10 one day and 4 the next, the latter uploads get written into a second row - ideally what I need is for the table to be locked down somehow so there's only one row which I'm updating each time.
So... my question, basically, is can this be done, or do I need to set my table up in a different way? I've got id as primary key, and wondered whether I ought to have set this to something different like unique, maybe?
Any assistance appreciated with this one - thanks in advance.
I've set up a series of "admin" pages for this table so that the user can create new records and update existing records - this works OK, but there's a small problem which I need some help with.
If the user were to make all 20 uploads in one go, that would be fine and all the data would be written into one row in the table. However, if he uploads (say) 10 one day and 4 the next, the latter uploads get written into a second row - ideally what I need is for the table to be locked down somehow so there's only one row which I'm updating each time.
So... my question, basically, is can this be done, or do I need to set my table up in a different way? I've got id as primary key, and wondered whether I ought to have set this to something different like unique, maybe?
Any assistance appreciated with this one - thanks in advance.
Comment