On 14/11/2018 13:25, Terry Coles wrote:
On Wednesday, 14 November 2018 12:40:46 GMT Ralph Corderoy wrote:
So if you've five widgets, two of them Condition=rusty, is that two
rows? What columns come together to make a unique row rather than one
that should be merged into another? I'd group those together rather
than slot Quantity in between, say.
I had to think about this to understand what you meant by your question. At
the moment Condition could have several entries; New or Used is the most
common, but Needs Assembly also appears (for example, Pis can come bare or
with pre-assembled headers).
When you talk about rows, do you mean rows in the spreadsheet or rows in the
database (is there such a thing)? In terms of the GUI, we would want some
kind of dropbox to select the condition I expect. If not it could be simply a
plain text entry. (There won't be many Users (at least at first).)
I take 'rows' to mean fields in the database Record.
Is Location brief enough to be entered consistently? Or should there be
a table of locations with precise descriptions, each with a unique ID,
either numeric or mnemonic, with the database or code enforcing each
Item row uses a valid Location ID?
Now, if you has a second table of locations, then if done correctly, adding
data to the location field in the first table would bring down a dropbox of
items from the second table. Similar for condition?
For this one the answer is much the same as for Condition.
Peter
--
Next meeting at *new* venue: Bournemouth, Tuesday, 2018-12-04 20:00
Check if you're replying to the list or the author
Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/
New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
