Opened 9 years ago

Closed 4 years ago

#294 closed improve feature (wontfix)

partly redundant DB tables 'members' and 'user'

Reported by: lemon-head Owned by:
Priority: minor Milestone: unassigned
Component: FrameWork Keywords: database, user, members
Cc:

Description

  • members.Username seems to coincide more or less with user.handle
  • members.id is very different from user.id !!
  • members listed in 'user' are associated with forum posts
  • 'members' has all the other user data
  • there are fewer members in 'user' then in 'members' (in my local test db)

If we want to change this, we need to dive into the forum code, because the 'user' table is heavily used there. Maybe we could even think about a redesign of the 'members' table structure. This one table is very big!

about members.id vs members.Username

Which one is better to use as a reference in other tables?

  • It is still possible that a member wants to change the username - in this case we would have to change it in every table. Here an id would be more reliable.
  • For searching, members will usually give us a username, not an id. So it would be an extra step to look up the id (but that's something we could live with).

Change History (6)

comment:1 Changed 5 years ago by steinwinde

  • freq_reported set to 1
  • Owner set to steinwinde
  • show_on_bw set to 0
  • Status changed from new to assigned

comment:2 Changed 5 years ago by steinwinde

  • Owner steinwinde deleted

comment:3 Changed 5 years ago by TimLoal

  • Milestone set to unassigned

comment:4 Changed 5 years ago by TimLoal

  • Component changed from BW General to FrameWork

comment:5 Changed 5 years ago by jsfan

  • Milestone Future deleted

Milestone Future deleted

comment:6 Changed 4 years ago by guaka

  • Milestone set to unassigned
  • Resolution set to wontfix
  • Status changed from assigned to closed

welen

Note: See TracTickets for help on using tickets.