Feature #71
Discussion: Record Keeping
| Status: | New | Start: | 10/23/2009 | |
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | - | Spent time: | - | |
| Target version: | - | |||
| Resolution: |
Description
So, I noticed, when we delete an item, it removes all instances of that item from our records, mainly repairs. Obviously, we want to keep records of these items (you could spend money on something during a year, but then get rid of it. You would still want to keep track that you had the item at one point).
Perhaps it would be good to not actually delete items, but just make that another field "deleted". It seems non-intuitive to keep records of stuff you don't own, but at the same time.. Hrm, I'm not sure. Thoughts?
History
Updated by Cameron Fackler 279 days ago
Seems to me that "lazy deletion" would be a good thing to have. Another thing that I'd like to add to the database is a field for whether inventory is "public" and can be seen by others. This will be good for when you can easily see a listing of all inventory, in case a club would like to keep track of things that are not available for lending.
A quick googling reveals that MySQL does not support the BOOLEAN type, so I'll have to think about how to implement these fields. Possibly a bitfield, but that could make for some ugly application logic.