QUOTE(DaytonRocker @ Sep 17 2003, 09:55 AM)
Not knowing the design of the software and database, I can only assume that the database normalization (getting both databases to balance) is more complicated than a simple entries (i.e. register entries). For example, I'm sure each transaction has an ID which probably has to match one ID in the other. Assuming these are created by triggers (in lieu of direct access or stored procedures), there can only be one transaction for each in each table.
You seem to be assuming a lot, and your assumptions seem just a tiny bit self-serving. You admit you don't know the design of the software at database, so your suppositions are no more credible than anyone else's.
QUOTE
if someone goes in a tries to change a number from 50,000 to 5000, a trigger would create another transaction.
Again you're assuming that triggers are being used. Does MS Access - the database in question here - even support triggers or stored procedures? Even if it does, do you have
anything at all to prove that the Diebold programmers use them? Even dedicated database weenies often don't use much more than simple inserts and selects, and the Diebold folks are likely to specialize in entirely different areas of computing. It would actually be a bit surprising to see an embedded-system programmer use triggers.
QUOTE
This is the double entry accounting method that someone here has discounted as "minutiae".
I didn't discount double-entry accounting
in toto as minutiae; I discounted the distinction between same information vs. information about the same transactions as minutiae. That was perfectly clear from the context, and whining about my dismissal of that meaningless distinction really doesn't help to move the debate along.
QUOTE
As if this isn't a "real" accounting method. Just some obscure type I stumbled upon on the web (nevermind I've owned my own business since the late 80's and much like most businesses, use double entry accounting). But I won't attempt to debate the methods they use here because we don't know all the details. But I can assure you it's not "two sets of books" as someone previously has intimated.
Appeal to (unverifiable) authority, followed by a strawman. I said that
what Diebold is doing is like having two sets of books. For someone who complained about being quoted out of context when you weren't, you seem awfully quick to spin others' statements into something unrecognizable.
QUOTE
One simple query could give you every transaction that doesn't match and you could get an entire report of what doesn't match. I have no doubt the voting commission gets that report and has been getting it in the states that are currently using this process.
Another assumption. Anything to back it up?
Anything at all? BTW, it's not just a simple query when the data reside in separate
databases - not tables - as in the Diebold case.
QUOTE
The paranoia is so bad, that Bev Harris and Co. states explicitly that C++ code is unsafe.
Proof by fallacy again. Bev Harris could be the biggest idiot in the world - OK, second biggest - and it still wouldn't prove your point.
QUOTE
Most of what you hear is based on software that was never released. The people making money off of book sales on this (umm...that would be Bev Harris again)
Enough with the
ad hominems already, Mr. Contracts-for-Diebold; try facts for once.
QUOTE
Personally (and like many programmers), I don't delete old code right away. I leave it there as a reference for later by commenting it out. It may not have ever worked. It may have had problems. But sometimes we keep it as our learning tool for later.
Do you typically put such intermediate versions of code in an archive on a website? No, I don't think you do, and I doubt Diebold does either. If it was on the FTP site, even if it wasn't meant for public consumption, it was there for
someone to get. Who? And why?
QUOTE
And a lot of stuff is just rumor and myth.
Yes, I agree, there has been far too much rumor and myth about how the software was designed, from people who know even less about it than Bev Harris. Let's stick to facts, shall we?