OK, so MySQL is more easily configured than Postgres? I must say the DBs I've set up have done fine with default configurations, both Postgres and MySQL. But I'll take your word for it that configuration is easier for your apps, which I assume are higher load than the defaults of either will handle gracefully. That sounds like a legit reason.
How could you know this? Every BAC tester I've seen says right on the label that it's not accurate except to detect whether or not there is any alcohol present.
Two drinks isn't much, either. That's one martini.
Bad driving should be penalized no matter what the reason. We should not have outrageous, life ending consequences for going safely home from the bar after two martinis.
Giving them the benefit of the doubt that their code doesn't go off executing random data, what is the probability that a "cosmic ray" will send a modern micro into crazy mode?
I imagine the intent is for database administrators to issue that command during scheduled maintenance windows. I agree that an "auto vacuum" feature would be preferable for many people. Is "auto vacuum" the major advantage of MySQL over Postgres, then?
I didn't ask if it worked. I asked in what scenario it would be a superior option (to the well-informed application architect, of course). The only real reason you gave is that you don't know much about Postgres. That means you're not really qualified to answer the question.
Does it scale better? Does it have better security? Is it easier to manage in some way? Is there a killer feature its two closest competitors lack? Those might be actual answers to the question. "I don't know much about it" is not an answer.
It's certainly commonly perceived that Postgres will scale better, and that it has a rather complete featureset. If this is indeed the case, I can't see a reason to select MySQL for a new project. Why limit yourself?
That's certainly a good thing, i'll give you that.
it plays nicely with Perl and PHP,
I just threw up. As my keyboard shorted in its vomit bath, it outputted a random string of characters and symbols, which just happen to execute without warnings when piped to perl.
For apps that need basic SQL functionality and aren't particularly-high load, I use SQLite. For app that need advanced SQL or high load, I use Postgres. I can't imagine a scenario when I would chose to use MySQL (or MS SQL, for that matter).
In embedded systems programming, it is common practice to disable interrupts if they are not used. It is certainly possible that this app simply does not need to handle these interrupts, whether they are enabled or not.
It is also possible that the other flaws mentioned, which clearly reduce accuracy, do not do so sufficiently to change the outcome in a meaningful way.
The problem with drunk driving law is not primarily one of testing. It is that it presumes someone is incapable of driving with even trace amounts of alcohol, while treating other forms of more dangerous driving (such as driving while texting or on the phone) as being OK or far far less severe.
The way the laws themselves are written is a horrible miscarriage of justice. This is the result of the perverse and hypocritical views of MADD and its ilk, the bastard children of the prohibition movement.
I imagine a USB voltage tester could be made by cutting a USB cable and connecting the wires to something you can easily snag with a basic $10 radio shack multimeter.
Go for it and post back. Either way, you should henceforth reconsider making claims of the form "X is faulty because X and Y don't work together" without verifying conclusively that Y is not faulty.
The thing is that if we're talking about a small difference it should be regulated away (the spec is 4.75 V to 5.25 V) whereas if it's a big difference I wouldn't expect ANY device to live (e.g. the 8V previously mentioned.)
This is false. More specifically, it is a false dichotomy. It implies that a voltage mismatch is either very small or very large, exclusively.
When running something out of spec, it is perfectly reasonable to expect some devices to be damaged and not others, depending on their tolerance levels. They should not be considered faulty unless they are damaged while operating in-spec.
FTP? The ancient protocol which sends all your data and your passwords in the clear for the internet to see? The protocol which provides only very limited remote operations and metadata to the client? The protocol which really should have died ten years ago? You pay for that?
Your troubleshooting skills are poor (as are those of the people who moderated you up).
When two pieces of technology don't work together, unless you have the equipment to actually test that they interface according to spec, you don't know which one is faulty/out-of-spec.
It is quite possible that your high-end OCZ drive is operating well within spec, but the other drives you tried simply have more tolerance for the faulty connection in your girl's car. High end, high speed silicon is naturally more sensitive, as it is smaller, so this would make sense.
It sounds like adults and police bullying an innocent kid. We've all been there, so of course we empathize. But, honestly, we don't have any verification that his story is accurate, and we know it is not impartial. I hope the kid finds a lawyer to press his issue pro bono, and I hope slashdot follows up. But I really don't think it is appropriate to immediately pass judgment about the issue.
Not in the US. Here, if you steal two lollipops, you can get charged with theft, trespassing, health code violations, unlicensed candy distribution, and disorderly conduct. And they might charge you with only some of those crimes or for just one lollipop. That way, they can prosecute you again if you are found not guilty the first time.
9h is indeed with low brightness and wired net access. It's also with a working keyboard! I hope you think fondly of the $50 you saved every time you go for the right-shift and hit the up-arrow:-P
OK, so MySQL is more easily configured than Postgres? I must say the DBs I've set up have done fine with default configurations, both Postgres and MySQL. But I'll take your word for it that configuration is easier for your apps, which I assume are higher load than the defaults of either will handle gracefully. That sounds like a legit reason.
How could you know this? Every BAC tester I've seen says right on the label that it's not accurate except to detect whether or not there is any alcohol present.
Two drinks isn't much, either. That's one martini.
Bad driving should be penalized no matter what the reason. We should not have outrageous, life ending consequences for going safely home from the bar after two martinis.
Giving them the benefit of the doubt that their code doesn't go off executing random data, what is the probability that a "cosmic ray" will send a modern micro into crazy mode?
I imagine the intent is for database administrators to issue that command during scheduled maintenance windows. I agree that an "auto vacuum" feature would be preferable for many people. Is "auto vacuum" the major advantage of MySQL over Postgres, then?
My ancestors invented the corndog. Everywhere I look, people are eating corndogs and not giving me money. Do I need a magic spell?
Yes, I am a carnie.
I didn't ask if it worked. I asked in what scenario it would be a superior option (to the well-informed application architect, of course). The only real reason you gave is that you don't know much about Postgres. That means you're not really qualified to answer the question.
Does it scale better? Does it have better security? Is it easier to manage in some way? Is there a killer feature its two closest competitors lack? Those might be actual answers to the question. "I don't know much about it" is not an answer.
It's certainly commonly perceived that Postgres will scale better, and that it has a rather complete featureset. If this is indeed the case, I can't see a reason to select MySQL for a new project. Why limit yourself?
That's certainly a good thing, i'll give you that.
I just threw up. As my keyboard shorted in its vomit bath, it outputted a random string of characters and symbols, which just happen to execute without warnings when piped to perl.
For apps that need basic SQL functionality and aren't particularly-high load, I use SQLite. For app that need advanced SQL or high load, I use Postgres. I can't imagine a scenario when I would chose to use MySQL (or MS SQL, for that matter).
In embedded systems programming, it is common practice to disable interrupts if they are not used. It is certainly possible that this app simply does not need to handle these interrupts, whether they are enabled or not.
It is also possible that the other flaws mentioned, which clearly reduce accuracy, do not do so sufficiently to change the outcome in a meaningful way.
The problem with drunk driving law is not primarily one of testing. It is that it presumes someone is incapable of driving with even trace amounts of alcohol, while treating other forms of more dangerous driving (such as driving while texting or on the phone) as being OK or far far less severe.
The way the laws themselves are written is a horrible miscarriage of justice. This is the result of the perverse and hypocritical views of MADD and its ilk, the bastard children of the prohibition movement.
I imagine a USB voltage tester could be made by cutting a USB cable and connecting the wires to something you can easily snag with a basic $10 radio shack multimeter.
Go for it and post back. Either way, you should henceforth reconsider making claims of the form "X is faulty because X and Y don't work together" without verifying conclusively that Y is not faulty.
This is false. More specifically, it is a false dichotomy. It implies that a voltage mismatch is either very small or very large, exclusively.
When running something out of spec, it is perfectly reasonable to expect some devices to be damaged and not others, depending on their tolerance levels. They should not be considered faulty unless they are damaged while operating in-spec.
FTP? The ancient protocol which sends all your data and your passwords in the clear for the internet to see? The protocol which provides only very limited remote operations and metadata to the client? The protocol which really should have died ten years ago? You pay for that?
And that, my friend, is the beauty and magic of complaining on slashdot.
Your troubleshooting skills are poor (as are those of the people who moderated you up).
When two pieces of technology don't work together, unless you have the equipment to actually test that they interface according to spec, you don't know which one is faulty/out-of-spec.
It is quite possible that your high-end OCZ drive is operating well within spec, but the other drives you tried simply have more tolerance for the faulty connection in your girl's car. High end, high speed silicon is naturally more sensitive, as it is smaller, so this would make sense.
That's what she said?
This is all part of your plan to starve H1Bs, isn't it?
Yeah, right. Trying to take credit for this fine AC's post, I see. We see through your ruse.
It sounds like adults and police bullying an innocent kid. We've all been there, so of course we empathize. But, honestly, we don't have any verification that his story is accurate, and we know it is not impartial. I hope the kid finds a lawyer to press his issue pro bono, and I hope slashdot follows up. But I really don't think it is appropriate to immediately pass judgment about the issue.
Not in the US. Here, if you steal two lollipops, you can get charged with theft, trespassing, health code violations, unlicensed candy distribution, and disorderly conduct. And they might charge you with only some of those crimes or for just one lollipop. That way, they can prosecute you again if you are found not guilty the first time.
"J.P. Morgan and Morgan Stanley led the bond sale."
http://www.marketwatch.com/story/microsoft-announces-first-ever-bond-offering
Sure, you can buy pieces on the secondary market. But that's true of just about anything.
No, this is the new chair fund. They're even building a chair-throwing range with moving targets.
JP Morgan Chase. They probably won't talk to you unless you have many thousands to invest, though.
So you've discovered a means to accelerate the gestation process?
9h is indeed with low brightness and wired net access. It's also with a working keyboard! I hope you think fondly of the $50 you saved every time you go for the right-shift and hit the up-arrow :-P
Or you could get a girlfriend...