Page 2 of 2
Re: Kyushu-Jangara 2017-09-12
Posted: Tue Sep 12, 2017 6:30 pm
by AnotherFairportfan
Dave wrote:And, since nobody else has said it, I will.
Tonkatsu ramen? Yummy!
Based on the reviews I've read, Lily's suggestion is an excellent one.
Can Wapsi vampires eat regular food?
=================
Duh.
Link to the answer was right there on the page...
I remembered that just as i hit "Submit"...
Re: Kyushu-Jangara 2017-09-12
Posted: Tue Sep 12, 2017 8:10 pm
by Warrl
Dave wrote:jwhouk wrote:AmriloJim wrote:And the addition of the Kitahara kozuko means the next iteration of JW's relationship chart will be a cork board covered with Pst-It notes.
Hey, I didn't say it was going to be EASY to keep that up.
Heck, just making it into a
database boggles the mind.
Well, that's a problem that the industry solved decades ago.
It's a relational database.
I know that's supposed to be a pun, but it actually is a pretty simple database design.
tPerson: PersonID autonumber primary key, PersonIdentity text
tPersonName: NameID autonumber primary key, PersonID foreign key, Name, StartDate optional date, EndDate optional date
(Yes, I threw in supporting one person having multiple names - aliases, marriages & divorces, adoptions, nicknames...)
tRelationshipType: TypeID autonumber primary key, TypeName text
tRole: RoleID autonumber primary key, TypeID foreign key, RoleName text
tRelationship: RelationshipID autonumber primary key, Description text, TypeID foreign key
tPersonRelationship: PRID autonumber primary key, PersonID foreign key, RelationshipID foreign key, RoleID foreign key, StartDate optional date, EndDate optional date
(I used to do this stuff for a living. And if anyone's aware of the debate over natural versus artificial primary keys, my position is that you try to avoid ever letting anyone even SEE the primary key, let alone enter it - because if they see it, it will acquire meaning; if it has meaning, it can be wrong or can change; and changing a primary key is a messy business.)
Re: Kyushu-Jangara 2017-09-12
Posted: Tue Sep 12, 2017 8:50 pm
by Dave
AnotherFairportfan wrote:Can Wapsi vampires eat regular food?
There's been no evidence introduced that any of the criminals that Suzi slaughtered and ate, were at all irregular.
I rather suspect that they proved otherwise, when they saw her enter the room.
Re: Kyushu-Jangara 2017-09-12
Posted: Tue Sep 12, 2017 9:49 pm
by AnotherFairportfan
Dave wrote:AnotherFairportfan wrote:Can Wapsi vampires eat regular food?
There's been no evidence introduced that any of the criminals that Suzi slaughtered and ate, were at all irregular.
I rather suspect that they proved otherwise, when they saw her enter the room.
{
Extremely Dignified Silence}
Re: Kyushu-Jangara 2017-09-12
Posted: Tue Sep 12, 2017 11:31 pm
by Atomic
Warrl wrote:(I used to do this stuff for a living. And if anyone's aware of the debate over natural versus artificial primary keys, my position is that you try to avoid ever letting anyone even SEE the primary key, let alone enter it - because if they see it, it will acquire meaning; if it has meaning, it can be wrong or can change; and changing a primary key is a messy business.)
It is by key alone I set my RDB in motion. It is by the 3rd Normal Form that transactions acquire speed, the queries acquire data, the data become an output. It is by key alone I set my RDB in motion.
Re: Kyushu-Jangara 2017-09-12
Posted: Wed Sep 13, 2017 4:19 am
by Just Old Al
Dave wrote:AnotherFairportfan wrote:Can Wapsi vampires eat regular food?
There's been no evidence introduced that any of the criminals that Suzi slaughtered and ate, were at all irregular.
I rather suspect that they proved otherwise, when they saw her enter the room.
Really? That was bad even for you.
Re: Kyushu-Jangara 2017-09-12
Posted: Wed Sep 13, 2017 9:15 pm
by Catawampus
I notice that Katherine is fine with casually referring to "mom". That is good.
oldmanmickey wrote:With the introduction of a Asian Fae as Pickles boyfriend and the college being in Tokyo anyone care to be how long before we see other members of his family?
Or the boy himself. He might end up becoming a friend of Atsali's, much to Castela's annoyance.
Re: Kyushu-Jangara 2017-09-12
Posted: Thu Sep 14, 2017 4:11 am
by TazManiac
Atomic wrote:Warrl wrote:(I used to do this stuff for a living. And if anyone's aware of the debate over natural versus artificial primary keys, my position is that you try to avoid ever letting anyone even SEE the primary key, let alone enter it - because if they see it, it will acquire meaning; if it has meaning, it can be wrong or can change; and changing a primary key is a messy business.)
It is by key alone I set my RDB in motion. It is by the 3rd Normal Form that transactions acquire speed, the queries acquire data, the data become an output. It is by key alone I set my RDB in motion.
(Whew!), thx for that. He started Coding and everything...
PS- Mentat
Mantra
Re: Kyushu-Jangara 2017-09-12
Posted: Thu Sep 14, 2017 11:34 pm
by Atomic
Anyone who insists on normalizing a database AND (re)setting the primary key to Zero after the initial data load is entirely too anal to work with. Really. I mean... really!!!
It's right up there with making your bed with hospital corners before heading to the Titanic lifeboats.
Re: Kyushu-Jangara 2017-09-12
Posted: Fri Sep 15, 2017 11:20 am
by Warrl
Atomic wrote:Anyone who insists on normalizing a database AND (re)setting the primary key to Zero after the initial data load is entirely too anal to work with. Really. I mean... really!!!
That's another advantage of not letting people see the primary keys. Who cares if your ten transaction types have ID numbers scattered from 83 to 207? Nobody ever sees those numbers anyway!
Re: Kyushu-Jangara 2017-09-12
Posted: Fri Sep 15, 2017 11:54 am
by Dave
If you really want to confound them, set up your primary keys as double precision floating point numbers, generated randomly. Anybody who tries to do a join based on key equality, will deserve what he gets (a pie in the face).

Re: Kyushu-Jangara 2017-09-12
Posted: Fri Sep 15, 2017 12:14 pm
by Atomic
Dave wrote:If you really want to confound them, set up your primary keys as double precision floating point numbers, generated randomly. Anybody who tries to do a join based on key equality, will deserve what he gets (a pie in the face).

Don't forget a regularly scheduled bubble sort to "optimize the database for faster access."
No - really. And the manager wondered why it kept getting slower as more records were added. After all, Windows Defrag worked wonders for his home computer....
Re: Kyushu-Jangara 2017-09-12
Posted: Fri Sep 15, 2017 1:00 pm
by Dave
Atomic wrote:Don't forget a regularly scheduled bubble sort to "optimize the database for faster access."
No - really. And the manager wondered why it kept getting slower as more records were added. After all, Windows Defrag worked wonders for his home computer....
A very carefully hand-optimized bubble sort, no doubt.

Re: Kyushu-Jangara 2017-09-12
Posted: Sun Sep 17, 2017 1:40 pm
by TazManiac
One of my most cherished industry t-shirts is the 'DBase III for Mac'; it's a cool graphic and entirely Vapourware...
I did develop a small Inventory Database back around 1990-ish, but other than helping my Dad with Punch Card runs at Stanford U., I hate programming...