I know favorite forum hack, but can anyone say me about this hacks(Favorite thread hack or favorite post hack). I think, it will be fine, when the user can store in a thread or a post and in the next session, he see this threads or post in a separate windows or in an separte area and he can delete this in this ares.

Anyone know this?

For instance. First version only for favorite thread.

quick and ...?
Add a field "favoritesthreads" in table "user".
There I add the threads, they can the user use with a new button under the table of the thread (Edit template.), with a script, which I started.
The various threads I implode and expplode with the php-function. When I use "OR" as "character who stand between the threads" I can use the whole field as the end of the sql-statement.
Is that an idea?

or .. make a favorite threads table that contains a userid field that corresponds to the user's id and a field that contains the threadid so it looks like:

[Edited by rangersfan on 08-02-2000 at 04:27 PM]

couldn't this be a potential resource hog?

Thread Hog? It is no different than what you did other than to make it more streamlined in its own table.

there are alot more threads than there are forums. A favorite forum listing can only have soo many things, but a favorite thread can have a ton of threads for each user. To me it seems like it could *potential* resource hog, if each user puts a ton of favorites.

But, I have no idea what I'm talking about, so it probably isn't :)

The only time it would be accessed is when the user goes to the "Favorite Thread" page that lists their threads. It would grab all their thread ids from the favorite table then look up the thread title in the thread table, a simple join could be used to accomplish this. It then shows the threads to the user.

But the whole email notification system needs to be reworked so that Favorite Threads are the threads that get email notification. Just like Fusetalk does it. So replying to a thread isn't needed to put it under Email Notification. I talk about it all the time so I should get to it an write it. I haven't donme it because it would require some major hacking to database to accomplish it.

I dont think, its a potential resource hog, but the dirty way to put this as an array in the user table its quicklyer. I think about 4000 user and 15 favorites per user - it can be a big table and I must search for relations in other big tables.

But, maybe I put this in a favorite table, i can put a field of kind in it and I can store favorite post too or or forums.
Your oppions?

well i just added the basic bookmark a thread thing someone here posted... so they just click a link to bookmark the thread

Yes, that is one possibility, but i wont, that the user can see her favorites in my forum as a part of the forum and because of this I must it store in the database!