News for hackers. Stuff that matters.

darnaut

Re:MySQL man pages license change is a bug on Wednesday June 19, 2013 @12:27PM (#5906502)
I'm referring to the source code that is used to build and generate the documentation available in that link. The MySQL documentation is written using the DocBook XML format.

Here is a link to an older version of the page where the documentation was available: http://web.archive.org/web/20121030130559/http://dev.mysql.c...

See "Documentation Repositories".

Re:MySQL man pages license change is a bug on Wednesday June 19, 2013 @11:06AM (#5905946)
No word yet on why the source code for the MySQL documentation is no longer publicly available. Was recently and silently made unavailable. This is much worse than a few man pages.
Re:MySQL man pages license change is a bug on Wednesday June 19, 2013 @11:03AM (#5905928)
The MySQL build team has a script that updates the license header in files that require it. Since the "different license" is actually the license of the documentation, from which the man pages are generated, it is possible that the script failed to update the licence text in the man pages.

Source: Ex-Oracle MySQL engineer.

Re:Brazil enacts new forest code on Wednesday October 24, 2012 @10:41AM (#4693117)
> our constitution remain mostly unchanged since '88

There have been 73 amendements to the constitution over 28 years. Experts on the subject usually point out that it actually changes too much and too often.

Re:Salesforce will hire 40-50 Postgres people on Monday October 22, 2012 @01:19AM (#4681953)
> Postgres has been quietly competent since before this generation of hipsters was born.

Nice sound bite but PostgreSQL (as we know) was first released around 1996.

Re:Salesforce will hire 40-50 Postgres people on Sunday October 21, 2012 @05:35PM (#4680928)
You mean the copyright notice? It was there before Oracle acquired Sun.
Re:Salesforce will hire 40-50 Postgres people on Sunday October 21, 2012 @05:12PM (#4680850)
Where's the evidence? The linked source refers to closing test cases, which makes it more closed source, not open core.

Also, it is highly entertaining that most PostgreSQL news here tend to dwell to MySQL.

The analysis is all nice and dandy, except for being wrong. Interrupted reads are retried, but only up to a certain amount which can be changed. The (perhaps not so good) default is to retry one time.
Re:PostgreSQL Rising on Saturday July 21, 2012 @03:36AM (#4274266)
Re:PostgreSQL Rising on Saturday July 21, 2012 @03:21AM (#4274242)
Re:PostgreSQL Rising on Saturday July 21, 2012 @03:14AM (#4274229)
> If you (or anyone else) can point out why this benchmark is false or misleading, I'm all ears.

You might want to check out the "Online DDL for InnoDB Tables" section of the manual, it should help with understanding the results. http://dev.mysql.com/doc/refman/5.6/en/innodb-online-ddl.htm...

Re:PostgreSQL Rising on Friday July 20, 2012 @08:26PM (#4273496)
> Postgres operates in a lot of markets that MySQL doesn't [..] like telecom and finance

MySQL cluster is highly popular in telecom. http://www.mysql.com/customers/industry/?id=78

Re:PostgreSQL Rising on Thursday July 19, 2012 @08:28PM (#4268787)
> Why else would they buy MySQL? And the licensing is not as strong as you may think.

To compete with Microsoft SQL Server and to further solidify their customer base (most Oracle customers already use MySQL).

Re:Security vulnerability in MySQL ubuntu on Monday June 11, 2012 @01:04AM (#4093291)
> This is why real C programmers use int as their bool type. :)

It has the same problem if a wider type (e.g. long) is assigned to it. Use _Bool instead.