On Tue, 2006-01-03 at 10:53 +1100, Kim Ryan wrote: > Hi Dave, thanks for the quick reply. My problem is a,b,c,d and e are the > most efficient > way to define they key. Because of the way the data is generated, they > are guaranteed to > always be unique at the row level. Also I need to sometimes query just > by a or b or c etc. > I could add an auto increment column, but this is introducing some > redundancy to each > row. Still, if it is the only way around the problem, it may be the best > solution.
It may not be the only way but Peter and I think it is the way that will cause you least pain. It's not that bad for redundancy because as soon as you add an id column to table x, you can simplify y: x: id, a, b, c, d, e y: id, f > Another idea I had was to use views to construct a virtual table all > the column > joins I need. Will Maypole display table views? Sorry, don't know that. It's been discussed before, I think, so it's worth searching the archives. Also the CDBI archives. Cheers, Dave ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Maypole-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/maypole-users
