<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Also, re-reading this, I think I pretty much said the same thing Joe
did.... ;-)<br>
<br>
This is why I need to think about this later - it's way too early in
the day for me to be making any sense... ;-)<br>
<br>
--Pat.<br>
<br>
<div class="moz-cite-prefix">On 12/19/2014 12:24 PM, Pat Barron
wrote:<br>
</div>
<blockquote cite="mid:54945F49.9080404@lectroid.com" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
I need to think about this for a bit, hopefully tonight after
work. I may have a bit more DB experience - but not by much. ;-)<br>
<br>
The one comment I have off the top of my head is that we should
probably use something else besides the e-mail address as a
primary key, since e-mail addresses may change. Maybe let the DB
auto-generate a sequence number when a contact is added (and use
that sequence number as the primary key). Since we do want to
include e-mail addresses (maybe just not as the primary key), I
would also suggest adding a constraint to prohibit more than one
row from having the same e-mail address, which I think will spare
us the possibility of some nasty bugs later on. I do agree with
keeping separate tables for people, and membership details, in
case any of the contact records don't actually have a membership
associated with them.<br>
<br>
Hopefully more later...<br>
<br>
--Pat.<br>
<br>
<div class="moz-cite-prefix">On 12/19/2014 12:16 PM, Joe Prostko
wrote:<br>
</div>
<blockquote
cite="mid:CAKfvZxzEwfqgjiFpdux4cVQ=iYBzenV8e-YNi+8qVoj7T+mbqg@mail.gmail.com"
type="cite">
<div dir="ltr">On Thu, Dec 18, 2014 at 11:59 PM, John Lewis <<a
moz-do-not-send="true" href="mailto:oflameo2@gmail.com">oflameo2@gmail.com</a>>
wrote:<br>
><br>
> I have a schema I designed in sqlite3 today. If you like
it I can port<br>
> it over to MariaDB.<br>
<br>
<div>
<div>Seeing as we're likely not going to be doing crazy
stuff like multiple table joins, we could probably get
away with just having one table with all of the various
columns. Also, I'm a bit rusty on SQLite, but it looks
like you're trying to use the email address as something
like a primary key. I don't think that is the best idea
ever, since email addresses change.<br>
<br>
</div>
In MariaDB, we'd just use an autoindexing primary key, and
go from there.<br>
<br>
In any case, being a DBA is not at all my specialty (so I'm
likely confused about the details), but I'd rather keep
things as simple as possible, even if it means more columns
in one table. Then again, it's better to do things right
the first time, so it might make sense to keep separate
tables like you suggested, depending on the needs of
different people.<br>
<br>
</div>
<div>I'm sure somebody with more knowledge will chime in to
give comments.<br>
</div>
<div><br>
</div>
- joe<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
wplug-internet mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:wplug-internet@wplug.org">wplug-internet@wplug.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.wplug.org/mailman/listinfo/wplug-internet">http://www.wplug.org/mailman/listinfo/wplug-internet</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
wplug-internet mailing list
<a class="moz-txt-link-abbreviated" href="mailto:wplug-internet@wplug.org">wplug-internet@wplug.org</a>
<a class="moz-txt-link-freetext" href="http://www.wplug.org/mailman/listinfo/wplug-internet">http://www.wplug.org/mailman/listinfo/wplug-internet</a>
</pre>
</blockquote>
<br>
</body>
</html>