Project

General

Profile

Bug #2815

remove user_entry table and use party instead

Added by Michael Lee about 13 years ago. Updated about 13 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
EntryDB
Target version:
Start date:
04/09/2007
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
2815

Description

Using the party table will better facilitate users in the database and not require users to enter themselves twice. Will need to add initials field to party for this.

History

#1 Updated by Michael Lee about 13 years ago

I should do this next.

#2 Updated by Michael Lee about 13 years ago

This will cause some problems for the importing tool.

#3 Updated by Michael Lee about 13 years ago

included special set of instructions for databases that are pre 2.0.6 on import.

#4 Updated by Michael Lee about 13 years ago

importing from older databases now works OK. Entry works fine, too without user_entry. I never liked my name for that table, anyway, so I'm glad it's gone for that reason, too. Best reason is that we don't have 2 tables to track similar data (party/users)

#5 Updated by Redmine Admin over 7 years ago

Original Bugzilla ID was 2815

Also available in: Atom PDF