Ummm. Are you aware of the fact that over 100,000 voters in Florida had their constitutional right to vote recinded by a Governer who hired a GOP run auditing firm to remove names from the roles?
That prior to the last election, this list was generated for about $80,000 or so, and each county had to individually remove people from the list after verbally affirming they were the right people? i.e. names were only removed after verification?
That the firm hired to remove names this last time was paid over $2,000,000 to remove the names, and the county clerks were told this list was accurate and to remove ALL the names without confirmation?
That this list contained names of people convicted of MISDEMEANERs in texas (Florida only removes the names of convited felons, and only while they are still serving their time or on probation?)
That over 80,000 names are known to have been removed that should not have, and the majority of these were democrats?
We don't have to worry about the machines just yet, as long as Jeb can get away with this and folks like you don't even notice.
But hey, your guy got elected, and that's all that really matters, huh?
MySQL is so full of little incompatibilities with SQL92 it's not even funny. Here's one (of about a hundred examples you can come up with if you scour the SQL92 spec and compare what it says to what MySQL does.)
SQL92 says that if you multiply two numerics with a precision of say x and y digits to the right of the decimal place respectively, the result should have x+y digits of accuracy to the right of the decimal point.
i.e.
create table test (num1 numeric (10,2), num2 numeric(10,3)); insert into test values (4.54,8.679); select num1*num2 from test;
you get 39.403 for an answer. You're supposed to get 39.40266 for an answer, but MySQL just chops off the extra digits, in clear violation of the SQL92 standard.
Because of this, it's unlikely MySQL will be used by anyone (with a brain and capable of testing MySQL for compliance anyway) in a financial application like Oracle or Postgresql would be suited for.
There are plenty of other issues with MySQL. Anyone who's used databases a lot before seeing MySQL just shakes their head and laughs at the idea that someone would use it to store critical data.
Just set up one good server running RAID5 with a tape drive, and use it's drives to "share" with the other systems. While a samba server may not be on every single box you have, Linux, BSD, and windows can all mount an SMB share, and that's 99% of your setup for most people.
SMB is not a bad protocol really, and Linux and BSD both do quite well running it as a server. Solaris, not so much, it's (Solaris') multi-thread preference means that the multi-process samba doesn't run so fast on it for large numbers of users.
You can also use NFS if there's no windows boxes to connect. It's really not all that bad.
I wouldn't run a database on either, as I always run them on local mirrored disk sets, then dump any databases to the RAID5 box for backup.
Just saying that if you're needing to share back and forth from one box to another, you may need an in-between box that's backed up, reliable and secure.
If you've never heard Red Holloway pick up some of his work. Never made a bad disc. His 60s work defined Acid Jazz, and his more modern discs are bluesly stuff with one or two acid jazz cuts.
And, of course, Weather Report 8:30, one of the greatest albums ever made.
I think somebody was modding today looking for anything nasty and calling it a troll.
Even I thought, dumbass has the captioning turned on. Poor guy, maybe next time he'll ask a 12 year old for help first. Of course, his shame is no lesser, just kept out of public view.
Whomsoever modded this as a troll was not paying attention. The author speaks the truth and is right. Mod him for flaming maybe, but not trolling.
Re:Cringley, Linus, and Christoph Hellwig
on
Today's SCO News
·
· Score: 1
OK, here's the list for outlook 2002: 2003-01-22: Microsoft Outlook 2002 V1 Exchange Server Security Certificate Information Leakage Vulnerability
2002-12-04: Microsoft Outlook 2002 Email Header Processing Denial of Service Vulnerability
2002-04-26: Microsoft Outlook HTML Mail Script Execution Vulnerability
2002-04-09: Microsoft VBScript ActiveX Word Object Denial Of Service Vulnerability
2002-03-22: Microsoft Outlook Disabled Cookies Setting Bypass Vulnerability
2002-03-22: Microsoft Outlook IFrame Embedded Media Player File Vulnerability
2002-03-21: Microsoft Outlook Javascript Execution Vulnerability
2002-03-21: Microsoft Outlook IFrame Embedded URL Vulnerability
2001-08-17: Microsoft Outlook Arbitrary Code Execution Vulnerability
2001-07-13: Microsoft Outlook Unauthorized Email Access Vulnerability
outlook 2000:
2003-02-28: Microsoft Outlook and Outlook Express Arbitrary Program Execution Vulnerability
2003-02-10: Multiple Vendor Email Client JavaScript Information Leakage Vulnerability
2002-04-26: Microsoft Outlook HTML Mail Script Execution Vulnerability
2002-04-09: Microsoft VBScript ActiveX Word Object Denial Of Service Vulnerability
2002-03-22: Microsoft Outlook Disabled Cookies Setting Bypass Vulnerability
2002-03-21: Microsoft Outlook Javascript Execution Vulnerability
2002-03-21: Microsoft Outlook IFrame Embedded URL Vulnerability
2001-08-17: Microsoft Outlook Arbitrary Code Execution Vulnerability
2001-08-15: Microsoft MSHTML.DLL Crash Vulnerability
2001-07-13: Microsoft Outlook Unauthorized Email Access Vulnerability
2001-06-05: Microsoft Outlook Express Address Book Spoofing Vulnerability
2001-03-11: Microsoft Outlook vcard Buffer Overflow Vulnerability
2001-02-27: Microsoft Outlook Vcard DoS Vulnerability
2001-01-22: Microsoft Outlook Concealed Attachment Vulnerability
2000-08-24: Microsoft Outlook Rich Text Format Information Disclosure Vulnerability
2000-07-20: Microsoft Outlook / Outlook Express Cache Bypass Vulnerability
2000-07-18: Microsoft Outlook / Outlook Express GMT Field Buffer Overflow Vulnerability
2000-06-24: Microsoft Internet Explorer and Outlook/Outlook Express Remote File Write Vulnerability
2000-05-11: Microsoft Office 2000 UA Control Vulnerability
2000-02-19: Microsoft Signed ActiveX Active Setup Vulnerability
1999-11-08: Microsoft ActiveX CAB File Execution Vulnerability
Outlook 98:
2001-08-17: Microsoft Outlook Arbitrary Code Execution Vulnerability 2001-07-13: Microsoft Outlook Unauthorized Email Access Vulnerability 2001-06-05: Microsoft Outlook Express Address Book Spoofing Vulnerability 2001-03-11: Microsoft Outlook vcard Buffer Overflow Vulnerability 2001-02-27: Microsoft Outlook Vcard DoS Vulnerability 2001-01-22: Microsoft Outlook Concealed Attachment Vulnerability 2000-08-24: Microsoft Outlook Rich Text Format Information Disclosure Vulnerability 2000-07-20: Microsoft Outlook / Outlook Express Cache Bypass Vulnerability 2000-07-18: Microsoft Outlook / Outlook Express GMT Field Buffer Overflow Vulnerability 2000-06-24: Microsoft Internet Explorer and Outlook/Outlook Express Remote File Write Vulnerability 2000-05-12: Microsoft Outlook 98 / Outlook Express 4.x Long Filename Vulnerability 2000-02-19: Microsoft Signed ActiveX Active Setup Vulnerability 1999-11-08: Microsoft ActiveX CAB File Execution Vulnerability 1999-11-04: Microsoft IE window.open Redirect Vulnerability 1999-06-01: Multiple Vendor Buffer Overflow in MIME-aware Mail and News Clients Vulnerability 1999-06-01: Auto-execution Of VBA code Vulnerability 1999-06-01: Microsoft IE4 Clipboard Paste Vulnerability
Of course, looking that up could have taken you all of ten seconds, and you wouldn't have your pithy little response.
Nice try. Come back and play when you got game.
Re:Cringley, Linus, and Christoph Hellwig
on
Today's SCO News
·
· Score: 4, Informative
You miserable little astroturfing git.
Here, look at this list of vulnerabilities for outlook express: (found at www.ntbugtraq.org)
2003-05-14: Multiple IMAP Client Integer Overflow Vulnerabilities 2003-05-13: Multiple Vendor Invalid X.509 Certificate Chain Vulnerability 2003-04-23: Microsoft Outlook Express MHTML URL Handler File Rendering Vulnerability 2003-02-28: Microsoft Outlook and Outlook Express Arbitrary Program Execution Vulnerability 2003-02-10: Multiple Vendor Email Client JavaScript Information Leakage Vulnerability 2003-01-29: Microsoft Outlook Express S/MIME Buffer Overflow Vulnerability 2002-09-09: Alleged Outlook Express Link Denial of Service Vulnerability 2002-07-29: Microsoft Outlook Express XML File Attachment Script Execution Vulnerability 2002-07-21: Microsoft Outlook Express Spoofable File Extensions Vulnerability 2002-07-19: Microsoft Outlook Express SMTP Over TLS Information Disclosure Vulnerability
Notice that there are several from JUST this year that are remote root exploits.
If you're gonna slag somebody by telling them how great and invulnerable lookout is, you might actually want to do some research first.
FYI, the native Windows port to 7.2.1 was made last year as a kind of "test bed" and the code from that port is being incorporated into 7.4, which goes into code freeze in another few weeks.
After that, windows will be a natively supported platform.
I call bs on your entire post. either that or you haven't touched Postgresql in well over two years.
Vacuums can be run while the database is in full operation. i know, I've done it.
the folks who test the Linux kernel for scalability under a database are switching FROM SAPdb TO Postgresql because it is faster and provides more load on the kernel than SAPdb.
If your performance degrades over time, you likely don't know how to vacuum, or need to reindex. Reindexing will be a non issue in 7.4, due out this summer.
Postgresql uses MVCC, if you design your database to update the same field over and over, you're going to have issues, because mvcc doesn't perform well when treated like a row locking database.
Postgresql has had hot backups since 7.1 came along, nearly three years ago.
Your comment is more half assed than the one you replied to, because your knowledge is hopelessly out of date, yet you still cling to it.
I wonder if someone could do a clean room implementation of the MySQL client / connection lib. Then it wouldn't be an issue.
I wouldn't mind the pure GPL play if it wasn't to extort more money out of companies using MySQL in an otherwise acceptable way but being stuck by this licensing of their client.
Postgresql's pure BSD license is preferable for most companies, and many do pick it over MySQL for that very reason.
FYI, there are many companies running gigabyte and terabyte size databases on postgresql in production.
There's a link to some of them here
600 Megs, how quaint.
Actually, the folks who are working on kernel tuning for database performance are switching FROM SAPdb to Postgresql because Postgresql is generally much faster, especially on multi-CPU machines.
A bit more trivia, Postgres, which decended from the same roots as ingress, also transitioned from QUEL to SQL, and that was when they changed the name to PostgreSQL.
MySQL is a non-free product AND a free product
on
SAP and MySQL Join Forces
·
· Score: 4, Interesting
So how should we refer to it?
funny thing is, they FUD the GPL on their own site, basically saying that if you write a commercial app that uses MySQL you HAVE to buy the commercial version.
Last I checked, trying to limit the scope of use of software covered by the GPL was in fact a violation of the GPL.
but MySQL is a favored child, so the FSF says nothing.
Re:SAP and MySQL - The Difference is in the Name!
on
SAP and MySQL Join Forces
·
· Score: 2, Informative
huh. I guess the docs on the mysql site must be wrong then. http://www.mysql.com/doc/en/What-is.html s ays:
The official way to pronounce MySQL is ``My Ess Que Ell'' (not ``my sequel''), but we don't mind if you pronounce it as ``my sequel'' or in some other localised way.
but hey, who reads the docs anyway, not a MySQL guru like you eh?:-)
PostgresSQL Replicator - http://pgreplicator.sourceforge.net/ An asynchronous replica engine that provides some data ownership models and many conflict resolution algorithms. [open source, GNU License]
Rserv - http://techdocs.postgresql.org/installguides.php#r serv Installation guide for triggers to provide Master/Slave replication.
Usogres - http://usogres.good-day.net/ Real time backup utility.
eRServer - http://www.erserver.com/ Enterprise replication server. Currently in Beta.
DBBalancer - http://sourceforge.net/projects/dbbalancer/ Load balancing multithreaded PostgreSQL connection pool that has a replication mode to keep load balanced backend servers in sync. Currently in Alpha.
Slashdot Mirror
So, did either one of you einsteinian genuises check out the one and only link in my article?
Wow, if IQ was dynamite, you two couldn't blow your own noses.
Ummm. Are you aware of the fact that over 100,000 voters in Florida had their constitutional right to vote recinded by a Governer who hired a GOP run auditing firm to remove names from the roles?
That prior to the last election, this list was generated for about $80,000 or so, and each county had to individually remove people from the list after verbally affirming they were the right people? i.e. names were only removed after verification?
That the firm hired to remove names this last time was paid over $2,000,000 to remove the names, and the county clerks were told this list was accurate and to remove ALL the names without confirmation?
That this list contained names of people convicted of MISDEMEANERs in texas (Florida only removes the names of convited felons, and only while they are still serving their time or on probation?)
That over 80,000 names are known to have been removed that should not have, and the majority of these were democrats?
We don't have to worry about the machines just yet, as long as Jeb can get away with this and folks like you don't even notice.
But hey, your guy got elected, and that's all that really matters, huh?
http://www.gregpalast.com/
Actually, the majority of Databases that claim SQL-92 compliance only claim entry level compliance.
MySQL is so full of little incompatibilities with SQL92 it's not even funny. Here's one (of about a hundred examples you can come up with if you scour the SQL92 spec and compare what it says to what MySQL does.)
SQL92 says that if you multiply two numerics with a precision of say x and y digits to the right of the decimal place respectively, the result should have x+y digits of accuracy to the right of the decimal point.
i.e.
create table test (num1 numeric (10,2), num2 numeric(10,3));
insert into test values (4.54,8.679);
select num1*num2 from test;
you get 39.403 for an answer. You're supposed to get 39.40266 for an answer, but MySQL just chops off the extra digits, in clear violation of the SQL92 standard.
Because of this, it's unlikely MySQL will be used by anyone (with a brain and capable of testing MySQL for compliance anyway) in a financial application like Oracle or Postgresql would be suited for.
There are plenty of other issues with MySQL. Anyone who's used databases a lot before seeing MySQL just shakes their head and laughs at the idea that someone would use it to store critical data.
Ever been to a web page where cheesy electro synth just started playing? Guess what, you were playing a midi file...
Just set up one good server running RAID5 with a tape drive, and use it's drives to "share" with the other systems. While a samba server may not be on every single box you have, Linux, BSD, and windows can all mount an SMB share, and that's 99% of your setup for most people.
SMB is not a bad protocol really, and Linux and BSD both do quite well running it as a server. Solaris, not so much, it's (Solaris') multi-thread preference means that the multi-process samba doesn't run so fast on it for large numbers of users.
You can also use NFS if there's no windows boxes to connect. It's really not all that bad.
I wouldn't run a database on either, as I always run them on local mirrored disk sets, then dump any databases to the RAID5 box for backup.
Just saying that if you're needing to share back and forth from one box to another, you may need an in-between box that's backed up, reliable and secure.
linux on the desktop ... it's a flop.
You mispelled teraflop... :-)
Well this certainly falls under the "duh" category. Freshly written code tends to have fewer bugs than older, well reviewed, well tested code.
Wow, next we'll learn how you shouldn't buy any Ford, GM, or Chrysler product in the first year of production.
If you've never heard Red Holloway pick up some of his work. Never made a bad disc. His 60s work defined Acid Jazz, and his more modern discs are bluesly stuff with one or two acid jazz cuts.
And, of course, Weather Report 8:30, one of the greatest albums ever made.
Stanley Clark, School Days
I've been running Linux for over four years on our servers.
Guess how many times I've been up at 4am due to a patch that botched my system?
Of course, you already know the answer is zero.
If someone needs a Windows server put online, they can find some other poor slob to keep it running, I'm out of that line of work.
I think somebody was modding today looking for anything nasty and calling it a troll.
Even I thought, dumbass has the captioning turned on. Poor guy, maybe next time he'll ask a 12 year old for help first. Of course, his shame is no lesser, just kept out of public view.
Whomsoever modded this as a troll was not paying attention. The author speaks the truth and is right. Mod him for flaming maybe, but not trolling.
OK, here's the list for outlook 2002:
2003-01-22: Microsoft Outlook 2002 V1 Exchange Server Security Certificate Information Leakage Vulnerability
2002-12-04: Microsoft Outlook 2002 Email Header Processing Denial of Service Vulnerability
2002-04-26: Microsoft Outlook HTML Mail Script Execution Vulnerability
2002-04-09: Microsoft VBScript ActiveX Word Object Denial Of Service Vulnerability
2002-03-22: Microsoft Outlook Disabled Cookies Setting Bypass Vulnerability
2002-03-22: Microsoft Outlook IFrame Embedded Media Player File Vulnerability
2002-03-21: Microsoft Outlook Javascript Execution Vulnerability
2002-03-21: Microsoft Outlook IFrame Embedded URL Vulnerability
2001-08-17: Microsoft Outlook Arbitrary Code Execution Vulnerability
2001-07-13: Microsoft Outlook Unauthorized Email Access Vulnerability
outlook 2000:
2003-02-28: Microsoft Outlook and Outlook Express Arbitrary Program Execution Vulnerability
2003-02-10: Multiple Vendor Email Client JavaScript Information Leakage Vulnerability
2002-04-26: Microsoft Outlook HTML Mail Script Execution Vulnerability
2002-04-09: Microsoft VBScript ActiveX Word Object Denial Of Service Vulnerability
2002-03-22: Microsoft Outlook Disabled Cookies Setting Bypass Vulnerability
2002-03-21: Microsoft Outlook Javascript Execution Vulnerability
2002-03-21: Microsoft Outlook IFrame Embedded URL Vulnerability
2001-08-17: Microsoft Outlook Arbitrary Code Execution Vulnerability
2001-08-15: Microsoft MSHTML.DLL Crash Vulnerability
2001-07-13: Microsoft Outlook Unauthorized Email Access Vulnerability
2001-06-05: Microsoft Outlook Express Address Book Spoofing Vulnerability
2001-03-11: Microsoft Outlook vcard Buffer Overflow Vulnerability
2001-02-27: Microsoft Outlook Vcard DoS Vulnerability
2001-01-22: Microsoft Outlook Concealed Attachment Vulnerability
2000-08-24: Microsoft Outlook Rich Text Format Information Disclosure Vulnerability
2000-07-20: Microsoft Outlook / Outlook Express Cache Bypass Vulnerability
2000-07-18: Microsoft Outlook / Outlook Express GMT Field Buffer Overflow Vulnerability
2000-06-24: Microsoft Internet Explorer and Outlook/Outlook Express Remote File Write Vulnerability
2000-05-11: Microsoft Office 2000 UA Control Vulnerability
2000-02-19: Microsoft Signed ActiveX Active Setup Vulnerability
1999-11-08: Microsoft ActiveX CAB File Execution Vulnerability
Outlook 98:
2001-08-17: Microsoft Outlook Arbitrary Code Execution Vulnerability 2001-07-13: Microsoft Outlook Unauthorized Email Access Vulnerability 2001-06-05: Microsoft Outlook Express Address Book Spoofing Vulnerability 2001-03-11: Microsoft Outlook vcard Buffer Overflow Vulnerability 2001-02-27: Microsoft Outlook Vcard DoS Vulnerability 2001-01-22: Microsoft Outlook Concealed Attachment Vulnerability 2000-08-24: Microsoft Outlook Rich Text Format Information Disclosure Vulnerability 2000-07-20: Microsoft Outlook / Outlook Express Cache Bypass Vulnerability 2000-07-18: Microsoft Outlook / Outlook Express GMT Field Buffer Overflow Vulnerability 2000-06-24: Microsoft Internet Explorer and Outlook/Outlook Express Remote File Write Vulnerability 2000-05-12: Microsoft Outlook 98 / Outlook Express 4.x Long Filename Vulnerability 2000-02-19: Microsoft Signed ActiveX Active Setup Vulnerability 1999-11-08: Microsoft ActiveX CAB File Execution Vulnerability 1999-11-04: Microsoft IE window.open Redirect Vulnerability 1999-06-01: Multiple Vendor Buffer Overflow in MIME-aware Mail and News Clients Vulnerability 1999-06-01: Auto-execution Of VBA code Vulnerability 1999-06-01: Microsoft IE4 Clipboard Paste Vulnerability
Of course, looking that up could have taken you all of ten seconds, and you wouldn't have your pithy little response.
Nice try. Come back and play when you got game.
You miserable little astroturfing git.
Here, look at this list of vulnerabilities for outlook express: (found at www.ntbugtraq.org)
2003-05-14: Multiple IMAP Client Integer Overflow Vulnerabilities
2003-05-13: Multiple Vendor Invalid X.509 Certificate Chain Vulnerability
2003-04-23: Microsoft Outlook Express MHTML URL Handler File Rendering Vulnerability
2003-02-28: Microsoft Outlook and Outlook Express Arbitrary Program Execution Vulnerability
2003-02-10: Multiple Vendor Email Client JavaScript Information Leakage Vulnerability
2003-01-29: Microsoft Outlook Express S/MIME Buffer Overflow Vulnerability
2002-09-09: Alleged Outlook Express Link Denial of Service Vulnerability
2002-07-29: Microsoft Outlook Express XML File Attachment Script Execution Vulnerability
2002-07-21: Microsoft Outlook Express Spoofable File Extensions Vulnerability
2002-07-19: Microsoft Outlook Express SMTP Over TLS Information Disclosure Vulnerability
Notice that there are several from JUST this year that are remote root exploits.
If you're gonna slag somebody by telling them how great and invulnerable lookout is, you might actually want to do some research first.
Plus, you wouldn't cluster postgresql, you'd just run it on a Sun E15k.
Don't forget interbase. It's a damned fine little dbms as well.
FYI, the native Windows port to 7.2.1 was made last year as a kind of "test bed" and the code from that port is being incorporated into 7.4, which goes into code freeze in another few weeks.
After that, windows will be a natively supported platform.
I call bs on your entire post. either that or you haven't touched Postgresql in well over two years.
Vacuums can be run while the database is in full operation. i know, I've done it.
the folks who test the Linux kernel for scalability under a database are switching FROM SAPdb TO Postgresql because it is faster and provides more load on the kernel than SAPdb.
If your performance degrades over time, you likely don't know how to vacuum, or need to reindex. Reindexing will be a non issue in 7.4, due out this summer.
Postgresql uses MVCC, if you design your database to update the same field over and over, you're going to have issues, because mvcc doesn't perform well when treated like a row locking database.
Postgresql has had hot backups since 7.1 came along, nearly three years ago.
Your comment is more half assed than the one you replied to, because your knowledge is hopelessly out of date, yet you still cling to it.
I wonder if someone could do a clean room implementation of the MySQL client / connection lib. Then it wouldn't be an issue.
I wouldn't mind the pure GPL play if it wasn't to extort more money out of companies using MySQL in an otherwise acceptable way but being stuck by this licensing of their client.
Postgresql's pure BSD license is preferable for most companies, and many do pick it over MySQL for that very reason.
FYI, there are many companies running gigabyte and terabyte size databases on postgresql in production.
There's a link to some of them here
600 Megs, how quaint.
Actually, the folks who are working on kernel tuning for database performance are switching FROM SAPdb to Postgresql because Postgresql is generally much faster, especially on multi-CPU machines.
A bit more trivia, Postgres, which decended from the same roots as ingress, also transitioned from QUEL to SQL, and that was when they changed the name to PostgreSQL.
So how should we refer to it?
funny thing is, they FUD the GPL on their own site, basically saying that if you write a commercial app that uses MySQL you HAVE to buy the commercial version.
Last I checked, trying to limit the scope of use of software covered by the GPL was in fact a violation of the GPL.
but MySQL is a favored child, so the FSF says nothing.
huh. I guess the docs on the mysql site must be wrong then.
s ays:
:-)
http://www.mysql.com/doc/en/What-is.html
The official way to pronounce MySQL is ``My Ess Que Ell'' (not ``my sequel''), but we don't mind if you pronounce it as ``my sequel'' or in some other localised way.
but hey, who reads the docs anyway, not a MySQL guru like you eh?
You mean like THESE replicators???
r serv
Astroturfer.
PostgresSQL Replicator - http://pgreplicator.sourceforge.net/
An asynchronous replica engine that provides some data ownership models and many conflict resolution algorithms. [open source, GNU License]
Rserv - http://techdocs.postgresql.org/installguides.php#
Installation guide for triggers to provide Master/Slave replication.
Usogres - http://usogres.good-day.net/
Real time backup utility.
eRServer - http://www.erserver.com/
Enterprise replication server. Currently in Beta.
DBBalancer - http://sourceforge.net/projects/dbbalancer/
Load balancing multithreaded PostgreSQL connection pool that has a replication mode to keep load balanced backend servers in sync. Currently in Alpha.