mg>hopefully quick answer
> nigel wood wrote:
> > Here's a rough table stucture. The indexes in events tables would be
> > TargetId.
mg>there would be need to be a 1:1 correspondence between
mg>TargetId index and Username..all of your other tables would need to know
mg>the TargetId which would have to be somehow lookedup
mg>best to stick with a non-unique index on Username which everyone can divine from
> firstName and lastName
But problably TargetId+EventDate probably eventId+event date
mg>i would suggest switching this to a comibination og Username + EventDate
> > as you found more uses/added paging.
> Well that didn't format very well :-( The tables structures are:
mg>pretty light structure ..what about contact and or demographic information for the
mg>this table maybe unnecessary as you can store the text directly into the table
> LogMesssageText (optional)
mg>i would substitute in Username for TargetId
mg>diskspace is cheap and the ability to store a long message text is cheap
mg>usually handled by appserver thru 'locale specific' resource properties
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=1
Windows Live™ SkyDrive™: Get 25 GB of free online storage.