[thesite] question about article update
.jeff
jeff at members.evolt.org
Tue Jun 26 02:40:17 CDT 2001
isaac,
:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
: From: isaac
:
: > god, pet peeve number one when it comes
: > to database design -- storing a list
: > of ids in a field. no offense -- yuck.
:
: no offense taken of course.
:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
didn't think there would be. thought i should add it for all the sensitive
ears out there that might think i was jumping your case unnecessarily hard.
:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
: is the alternative another table in the database,
: and then a sequencing column also to allow ordering
: items within a set?
:
: ie, CONTENT table, ITEMSET, and then the table in
: between?
:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
yes, an association table where you store itemset_id and content_id. you'd
have a row for every unique combination. like you suggested, you could even
throw in a rank column for storing the order of the items.
:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
: (not too late to change if you think it's an utterly
: critical matter - just want to avoid overly
: complicating things (especially on the administrative
: side). actually, now that i think about it a bit more,
: maybe the extra table with many-to-many r'ships is the
: better solution :p)
:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
in the long-run, yes it's a better solution. it will actually save you
coding time later on.
:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
: other remaining features of low priority include
: scheduling, endaction (specify what happens to an
: item when it reaches its enddate), etc.
:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
don't forget things like notifications (email, page, sms), and task
management (i'm a publisher and assign you the editor a basic task on a
particular document).
good luck,
.jeff
http://evolt.org/
jeff at members.evolt.org
http://members.evolt.org/jeff/
More information about the thesite
mailing list