Come on!!!
If the Robots had broken say Newton's second law of motion, now that would be news, but Asimov's first law of robotics!
These are not actual laws that nature follows, robot's couldn't care less about humans unless they are told so. And like some wrote these robots are not "autonomous", the call to attack and what attack is made by humans.
"Simple web shit, sure, mysql is the way to go. But mysql's query optimizer still wets the bed for serious data churning. If you have heavy lifting to do and don't have the money for Oracle postgres is golden."
right on.
MySql should be considered for things that only need to be structured a little better than a plain textfile when the number of entries renders the textfile approach not practical. This is say webapps where you only need to save name/email/address, etc. For this MySql is better and faster than Postgres and therefore a better option.
For applications whose main need is to have a large number of complex related data stored, don't even think MySQL here.
Specially if your queries use a lot of joins (say 3 or more). Postgres is the way to go. Good performance, better data integrity and many more (used/usefull) features. If you do a lot of delete/updates then you'll have to have a good "cleanup" procedure or performace will become very low. This can be done on the fly and usually during a time period where data isn't much used (most usages have a period where access is low, but not all).
Version 4 was a great improvement on almost all of this.
Slashdot Mirror
Come on!!! If the Robots had broken say Newton's second law of motion, now that would be news, but Asimov's first law of robotics! These are not actual laws that nature follows, robot's couldn't care less about humans unless they are told so. And like some wrote these robots are not "autonomous", the call to attack and what attack is made by humans.
"Simple web shit, sure, mysql is the way to go. But mysql's query optimizer still wets the bed for serious data churning. If you have heavy lifting to do and don't have the money for Oracle postgres is golden."
right on.
MySql should be considered for things that only need to be structured a little better than a plain textfile when the number of entries renders the textfile approach not practical. This is say webapps where you only need to save name/email/address, etc. For this MySql is better and faster than Postgres and therefore a better option.
For applications whose main need is to have a large number of complex related data stored, don't even think MySQL here.
Specially if your queries use a lot of joins (say 3 or more). Postgres is the way to go. Good performance, better data integrity and many more (used/usefull) features. If you do a lot of delete/updates then you'll have to have a good "cleanup" procedure or performace will become very low. This can be done on the fly and usually during a time period where data isn't much used (most usages have a period where access is low, but not all).
Version 4 was a great improvement on almost all of this.
"Leveraging the long tail through customer self-service"
What the hell is that supposed to mean?!?
Kind of reminds me of a like back the whole friendster security policy thing.
0 0
some one at friendster actually said.
"We have a policy that we are not being hacked."
This is very similar, only in reverse.
http://slashdot.org/article.pl?sid=03/08/13/23382
If being poor is having less wealth than the average, then in all likelihood poverty will always exist.
Now what can be tried is to increase the quality of life in the low end of the wealth spectrum.
To a degree that has been achieved in the last 100/150 years.