(no subject)

Date: 2017-09-17 05:05 am (UTC)
laisserais: kiss (Default)
From: [personal profile] laisserais
So your field headers would be:

Vidder Name | Confirmed (y/n) | Name of Vid | etc

and the data would populate like so (each return is a new row):

Morgan Dawn | Y | your-vid-name | etc
Unknown | N | another-vid-name | etc
Mary Sue Lamb | N | another-vid-name | etc

and you're probably not gonna like this, but to handle multiple guesses, the best way to do it is to create a new row for each guess, with only the vidder name being different.

That's not intuitive, because it feels like it's redundant--and if you're only ever gonna be using this for personal use and only reading it with your eyes, then you don't have to--but if this is ever going to grow or be used as an actual database, then it's best to do it that way. I call it 'machine readable' -- it's called first normal form.

In an actual database, you'd want to do this and attach a unique identifying number to every vid name and every vidder name.

Doing it like that will also help you set up pivot tables, where you can condense info and sort quickly.
If you don't have an account you can create one now.
HTML doesn't work in the subject.
More info about formatting

If you are unable to use this captcha for any reason, please contact us by email at support@dreamwidth.org

Profile

morgandawn: (Default)
morgandawn

January 2025

S M T W T F S
   1234
567891011
12131415161718
19202122232425
2627282930 31 

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags