Topic awaiting preservation: Trickiest MySQL Challenge Yet... |
|
---|---|
Author | Thread |
Paranoid (IV) Inmate From: Minneapolis, MN, USA |
posted 12-07-2001 19:55
Well, I appreciate all the help with my previous questions. Now I am just asking a question as a challenge to all of you. For simplicity's sake, examine this table structure modeling a many-to-many relationship: |
Maniac (V) Mad Scientist with Finglongers From: Cell 53, East Wing |
posted 12-07-2001 20:06
Perhaps DISTINCT in your mySQL? |
Paranoid (IV) Inmate From: Minneapolis, MN, USA |
posted 12-07-2001 20:32
The rows are already distinct. It's either a problem of the information spread across too many rows or not enough information. Here's my post from the devshed forums, it is a bit simpler to understand I think: |
Paranoid (IV) Mad Scientist From: Somewhere over the rainbow |
posted 12-07-2001 20:55
The poster has demanded we remove all his contributions, less he takes legal action. |
Maniac (V) Mad Scientist with Finglongers From: Cell 53, East Wing |
posted 12-07-2001 21:05
jiblet: Have I missed the point - you have tried SELECT DISTINCT etc. and it didn't work? I've had similar problems and this sorted it out no problems. If you have tried it then its is different problem or I'm thinking of a different function. |
Paranoid (IV) Inmate From: Minneapolis, MN, USA |
posted 12-07-2001 22:46
Well, the ACTUAL query SELECTS 20 fields from 9 tables with 7-15 where clauses (dynamically generated), but yes it uses SELECT DISTINCT. It's far too complicated to ask anyone to debug it, so I posted a simple case so that I could integrate the solution myself (if it is possible). |