Peter, Thank you ! I like that suggestion of graying out the button!
Stuart --- Peter Brawley <[EMAIL PROTECTED]> wrote: > Stuart, > > If one member may have a max of three resumes, then > the relationship is > one-many with cardinality=3, implementable with a > foreign key in resumes (eg > resumes.memberID). MySQL doesn't have tools for > implementing cardinality > constraints, so you would have to do that in > application code, ie grey out > the add-a-resume button for members whose resume > count exceeds 3. > > PB > ----- Original Message ----- > From: Stuart Felenstein > To: Rhino ; [EMAIL PROTECTED] > Sent: Thursday, September 02, 2004 12:05 PM > Subject: Re: After I went searching > > > Yep, understand about the 0 and checked the code > no > -1's. All is weird, but here is a situation that > in > the back of my mind I keep thinking maybe I need a > many to many. The problem is I "again" can't > quite > conceptualize it. If I'm making a rehash again , > I > really apologize. > Here is the situation: > > I have a table that hold resumes , each member can > store 3 resumes. > the table: > ResTable(myisam) > AndNextID - (auto inc) just really a counter and > PK > MemberID - > Resume Title - > Resume - > > So if they hit their three a trigger which does a > count on their records by their ID returns an > error > message. > The problem I'm running into now is on updating. > I'm > really trying not to confuse app logic and > mechanics > with the database. So I'll cut to the quick. > > ResTable1 > .......(same fields as above) > ResTable2 > ........(yadda yadda) > > Member_ResTable > Member (well actually not sure what would be in > here) > > Shawn, if your out there - I'm not ignoring your > advice to stave off the coding for now , > concentrate > on the db design. I just haven't come to grips > with it > yet! LOL > > Stuart > > Would there be a benefit in a: > > --- Rhino <[EMAIL PROTECTED]> wrote: > > > Formatting shouldn't be an issue if you entered > the > > query exactly as you > > said you did. However, I'm a little dubious that > you > > did; the error message > > seems to be saying that you have a negative sign > in > > front of the first 1 in > > the Limit clause. > > > > Check your typing and try the query again. Also, > > remember that the row > > numbers used by the Limit clause start with 0, > not > > with 1. In other words, > > you may want to try "Limit 0,1", not "Limit > 1,1". > > > > Rhino > > > > ----- Original Message ----- > > From: "Stuart Felenstein" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Thursday, September 02, 2004 12:18 PM > > Subject: Re: After I went searching > > > > > > > The query works fine on it's own, but > generates a > > SQL > > > error in my page: > > > > > > SELECT * > > > FROM MemberRez > > > WHERE LurkID=colname (I've tried it without > this > > line) > > > ORDER BY andnext asc limit 1,1 > > > > > > andnext is the pk auto inc. > > > > > > Page error: > > > You have an error in your SQL syntax. Check > the > > manual > > > that corresponds to your MySQL server version > for > > the > > > right syntax to use near 'LIMIT -1' at line 1 > > > > > > Maybe formatting ? > > > Stuart > > > > > > > > > > > > > > > --- Stuart Felenstein <[EMAIL PROTECTED]> > wrote: > > > > > > > Wait!!!!!!!!!!!!!! Don't answer...it's that > > LIMIT > > > > thing. > > > > > > > > > > > > :) > > > > Stuart > > > > > > > > > > > > --- Stuart Felenstein <[EMAIL PROTECTED]> > > wrote: > > > > > > > > > I'm tring to extract all records belonging > to > > one > > > > ID > > > > > in a table. > > > > > BUT! I want to do it in piece meal. > Meaning a > > > > > record > > > > > at a time. > > > > > I am assuming I need some kind of count > > mechanism. > > > > > > > > > > Example: > > > > > I want to see the first 3 purchases this > > member > > > > > made. > > > > > Instead of grabbing them all in one shot, > I > > want > > > > to > > > > > break those 3 out in 3 seperate results > set > > > > > > > > > > Results Set1: Purchase 1 > > > > > Results Set2: Purchase 2 > > > > > Results Set3: Purchase 3 > > > > > > > > > > This is probably easy. > > > > > > > > > > Thank you, > > > > > Stuart > > > > > > > > > > -- > > > > > MySQL General Mailing List > > > > > For list archives: > > http://lists.mysql.com/mysql > > > > > To unsubscribe: > > > > > > > > > > > > > > > > http://lists.mysql.com/[EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > -- > > > > MySQL General Mailing List > > > > For list archives: > http://lists.mysql.com/mysql > > > > To unsubscribe: > > > > > > > > === message truncated === -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
