I did that as a convenience. Basically it provided me two ways of uniquely
identifying any row in a table(an auto_inc integer, and some unique text
column). The autoincremented values should never repeat. HOWEVER because I
did not put a UNIQUE constraint on them, it is possible for someone to
Never mind, finally figured it out on my own.
Sorry , i think out loud sometimes!
Stuart
--- Stuart Felenstein [EMAIL PROTECTED] wrote:
Trying to figure out how this gets done. Let me
explain first. By the way I hope this is not off
topic
as perhaps it is more towards application then
Stuart,
You need to begin to divorce these two processes from each other: STORAGE
and INPUT/OUTPUT. What your user's see on a web page doesn't need to look
anything at all like your database structure. A user interface (UI) is
designed for ease of use. The other is designed for query and
Too funny! I'm slowly coming to grips on the M2M. I
decided not to opt for it in this situation as I still
believe it would not address my issues.
My problem, or a better to phrase it , my solution is
that I am not supplying titles. They are, to the user
, blank fields , left to them to supply
Trying to figure out how this gets done. Let me
explain first. By the way I hope this is not off topic
as perhaps it is more towards application then core db
.
I have a table:
Count[int][auto-increment], MemberID[int],
Title[varchar], TitleYear[int]
In my organization members can have or have
