On 9/15/04 10:51 PM, "Chris" <tclug at cmulcahy.com> wrote: > You do have the problem of varchar/integer values. On the > workout_attribute table, you can store another column which identifies > what type of data you are storing, then in the join_workout_attribute > table, you would have two value columns, one for integer, one for > varchar. You could use PostgreSQL rules to make sure you don't > accidentally stuff a value into the integer column when the attribute > should be a varchar. Chris, thanks again for the helpful information. One note: I am using MySQL for this project. I thought it would be good to get a little experience with that RDBMS. -Tim -- Tim Wilson Twin Cities, Minnesota, USA Educational technology guy, Linux and OS X fan, Grad. student, Daddy mailto: wilson at visi.com aim: tis270 public key: 0x8C0F8813 _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota Help beta test TCLUG's potential new home: http://plone.mn-linux.org Got pictures for TCLUG? Beta test http://plone.mn-linux.org/gallery tclug-list at mn-linux.org https://mailman.real-time.com/mailman/listinfo/tclug-list