truelove's ramblings

So I work at a software company. The software we make, we also support. I am one of the support monkeys.

We, the support monkeys, need to get into the databases of our clients on a regular basis and so I have acquired a working knowledge of SQL queries and update statements. This has in turn led to me acquiring a working knowledge of our databases's structure. Those of you who know programming probably can see where this is headed, generally.

For the rest of the class, first, you have to understand, the records we create in our software have two attributes. Call them zuzzles and miffle-snargs. Zuzzles can have associated to them a default miffle-snarg so that when you choose your zuzzle, the miffle-snarg is automatically filled in. The miffle-snarg can be changed, as it happens; the default is just, well, the default.

So here's the beautiful thing about our database. The table that contains all the zuzzles is named mifflesnarg. The table that contains the miffles-snargs is named trouslesnargs.

Yes, they really did call the zuzzle database table the *same thing* as an entirely different attribute which in turn is named something else in the database. And yes, the lack of consistency in pluralization I portrayed above is accurate.

You see why it is probably a good thing that I do not have access to a time machine. It would end poorly for our database's architect(s).