Slashdot Mirror

mysql_connect() is supposed to connect to a unix-domain socket, not an IP address.

Got a reference for that?

Socket based connections weren't added until 3.x.

mysql_connect() is supposed to connect to a unix-domain socket, not an IP address.

Got a reference for that?

Socket based connections weren't added until 3.x.

* For whatever reason, the default collation is not case-sensitive. This caused some interesting bugs when we least expected.

MySQL's default collation is ALSO case insensitive (note the trailing _ci).

When a client performs a large SELECT on a MyISAM table, it obtains a read lock on the data. Until the SELECT completes, the server won't release the lock and service any pending write requests for the table.

When a client performs a large SELECT on a MyISAM table, it obtains a read lock on the data. Until the SELECT completes, the server won't release the lock and service any pending write requests for the table.

When a client performs a large SELECT on a MyISAM table, it obtains a read lock on the data. Until the SELECT completes, the server won't release the lock and service any pending write requests for the table.

You might want tocheck it out a bit more ... TFA isn't all that accurate.

MySQL Enterprise is more than just the monitoring software ...

MySQL Enterprise

Database. Monitoring. Support.

The MySQL Enterprise subscription is the only comprehensive offering of production support, monitoring tools and MySQL database software to deliver optimal performance, reliability, security, and uptime. MySQL Enterprise includes:

MySQL Enterprise Server

The MySQL Enterprise Server software is the most reliable, secure and up-to-date version for cost-effectively delivering production database applications. Subscribers receive monthly rapid updates and quarterly service packs with the latest fixes.

MySQL Enterprise Monitor

The MySQL Enterprise Monitor software provides a "Virtual DBA that monitors production database applications and minimizes security vulnerabilities, improves replication, and optimizes performance.

MySQL Production Support

MySQL Production Support enables you to maximize the availability of your database applications. Plus, with Consultative Support, receive practical advice on how to optimize your configuration, replication set-up, schema, and queries for better performance.

Contrary to what the article summary might have led some to believe, its not just a piece of software that's being made available. If you follow the link, you'll find additional links and information. Hope this helps make things a bit clearer :-)

Check out the MySQL commercial license. It's pretty clear that any kind of distribution or connection method falls under the commercial license. The example you mentioned should be requiring the customer to purchase a license for MySQL, but in reality that will rarely happen if it's up to the installer.

Sounds like you want this + a large amount of consulting. Seriously, call a sales rep. I am sure MySQL will take as much money as you want to spend.

http://mysql.com/products/enterprise/unlimited.html

It was developed by such guys as Sanja Byelkin http://dev.mysql.com/tech-resources/interviews/sanja.html , Andi Gutmans http://en.wikipedia.org/wiki/Andi_Gutmans , and others.

It just works. It was created by these obscure, modest, but incredibly talented people, with minimal resources.

True, the MySQL was bought recently by the SUN. I have no doubt, it will become before long similar to IE8. A show run by MBAs in smart suits. A technology, which works not for you, but against you, on the side of the MBAs.

I do not know how to do it, but the world community should learn how to empower the people like Sanja Byelkin and Andi Gutmans. People are sick and tired of the browser monopolies with their incompatibilities, bugs, noncompliances with the standards. Something should be done about it by the world community.

If there is anything that I have learned in the past 10 years of writing code (since before high school), I have learned that the following sequence of learning is ideal.
1. HTML/CSS/JavaScript - Get acquainted with web programming. None of that Nambly-pambly BBCode crap that they offer on MySpace.
2. Python - I wish I had got into this before I learned C++. Good for learning about shells if you decide to switch to Linux or BSD, especially if you decide to create your own website through a webhosting provider that uses SSH.
3. C/C++ and/or PHP/MySQL. - Playing with the big-boy toys at this point. The safety net that points 1 and 2 provided has been lowered.
4. OpenGL or Assembly Programming. - Really advanced programming! OpenGL is high-level. Assembly is low-level.
From there on, the sky is the limit.

Very true.

This is why MySQL AB turned around and bought solidDB, and started writing Falcon in-house, a new transactional engine.

You are basing your belief on VERY old data.

http://forums.mysql.com/read.php?97,18003,18003

This post was made in March, '05, so for the "5 years now" puts it back to 2000.

HTH

Forrest

And the Innobase licensing has a time limit.

MySQL dropped BerkeleyDB support back in version 5.1.12 (24 October 2006). MyISAM is still the default engine, and for many common applications is still a good choice. They are exposed long-term over the InnoDB purchase, but only for transactional apps, and there are several good candidates available that might replace it. Oracle are in no hurry to bury a major revenue source until the strategic advantages of doing so outweigh the short-term benefits of selling InnoDB into companies that wouldn't have bought Oracle anyway.

MySQL dropped BerkeleyDB support back in version 5.1.12 (24 October 2006). MyISAM is still the default engine, and for many common applications is still a good choice. They are exposed long-term over the InnoDB purchase, but only for transactional apps, and there are several good candidates available that might replace it. Oracle are in no hurry to bury a major revenue source until the strategic advantages of doing so outweigh the short-term benefits of selling InnoDB into companies that wouldn't have bought Oracle anyway.

MySQL dropped BerkeleyDB support back in version 5.1.12 (24 October 2006). MyISAM is still the default engine, and for many common applications is still a good choice. They are exposed long-term over the InnoDB purchase, but only for transactional apps, and there are several good candidates available that might replace it. Oracle are in no hurry to bury a major revenue source until the strategic advantages of doing so outweigh the short-term benefits of selling InnoDB into companies that wouldn't have bought Oracle anyway.

Which MySQL do you use?

Read up. Disable autocommits, issue a BEGIN TRANSACTION, and make sure you check the success of all queries before you perform that COMMIT.

well, it would be weird if they just tucked together all the different acquisitions :)
though it isn't impossible - there's a relatively new thing, embedded mysql : http://www.mysql.com/products/embedded/.
frankly, i'd welcome such an option aside current java solution.

They did in 2006 and found about 0.224 defects per TLOC.

MySQL uses Coverity and Klockwork on their certified versions on several different platforms. The certified versions are based on the major releases of community versions, and are typically just more conservative in that they only make changes for critical and security bugs.

There's speculation that the community edition tested was actually an old report without a retest even back then, as the certified version based on that community version had zero defects reported and the bug count on the community edition was the same per TLOC as the previous report before those bugs were fixed in both versions.

Here is some more about Google and MySQL: http://www.mysql.com/customers/customer.php?id=75

Erm, I suggest you go away and read it, right back at you :)

http://www.mysql.com/company/legal/licensing/

"For OEMs, ISVs, and VARs who distribute MySQL with their products, and do not license and distribute their source code under the GPL, MySQL provides a flexible OEM Commercial License"

See. If we distribute MySQL with our software, we need a commercial licence unless we distribute our source code under the GPL.

Also, if you link with the MySQL client libraries - those also use GPL, so you have to distribute the source code to your product. See http://www.mysql.com/company/legal/licensing/faq.html, the section titled "Previously, the MySQL client libraries were licensed under the LGPL (the Lesser General Public License) and now they use the GPL (the General Public License)."

So, it's pretty hard (ie impossible) to use MySQL without either getting a commercial licence or releasing your own source code under the GPL (or other FOSS licence - using their FOSS licence exception)

If you are doing otherwise, watch out!

If you are selling a scripted solution (PHP,Python etc) and require the user to download and install MySQL themselves, you're probably OK, but if you are linking with their client libraries directly and/or distributing MySQL with your own software, you will fall foul of their licencing.

So - that's why we use PostgreSQL or SQLite (depending on requirements) instead. Licencing is MUCH easier.

Erm, I suggest you go away and read it, right back at you :)

http://www.mysql.com/company/legal/licensing/

"For OEMs, ISVs, and VARs who distribute MySQL with their products, and do not license and distribute their source code under the GPL, MySQL provides a flexible OEM Commercial License"

See. If we distribute MySQL with our software, we need a commercial licence unless we distribute our source code under the GPL.

Also, if you link with the MySQL client libraries - those also use GPL, so you have to distribute the source code to your product. See http://www.mysql.com/company/legal/licensing/faq.html, the section titled "Previously, the MySQL client libraries were licensed under the LGPL (the Lesser General Public License) and now they use the GPL (the General Public License)."

So, it's pretty hard (ie impossible) to use MySQL without either getting a commercial licence or releasing your own source code under the GPL (or other FOSS licence - using their FOSS licence exception)

If you are doing otherwise, watch out!

If you are selling a scripted solution (PHP,Python etc) and require the user to download and install MySQL themselves, you're probably OK, but if you are linking with their client libraries directly and/or distributing MySQL with your own software, you will fall foul of their licencing.

So - that's why we use PostgreSQL or SQLite (depending on requirements) instead. Licencing is MUCH easier.

[pedantic mode: on]
Had a hard time with the blurb for that matter. if you are going to mention the name of a product several times, please learn how it's written!

MySQL
Not mySQL. For that matter, not mySQL, MYSQL, MY-SQL, or mSQL (that's another program actually)

It's all over their website. Something that simple will help keep you from sounding amateurish as a reviewer.
[pedantic mode: off]

• Give some money to MySQL AB for this marvellous product that helps us make money too
• Dump MySQL and port to another RDBMs which may also go AGPL (Postgres) or cost lots of money (MS, Oracle, etc)
• Write our own MySQL compatible client library
• Post our source in compliance to AGPL, thus contributing in a way other than money

I don't think it is accurate it say MySQL is more secure than MSSQL. MySQLs security track record is abysmal at best. I at least cite sources to backup my retoric.

http://forge.mysql.com/wiki/Security_Vulnerabilities_In_MySQL_Server

1. Not all applications need to be "web apps"
2. Not all data is all that "critical"
3. DB engines support encrypted connections via SSL Here's how for mysql - you can REQUIRE the connection be secure.

   MySQL allows encryption to be enabled on a per-connection basis. You can choose a normal unencrypted connection or a secure encrypted SSL connection according the requirements of individual applications.

   Secure connections are based on the OpenSSL API and are available through the MySQL C API. Replication uses the C API, so secure connections can be used between master and slave servers.

4. the db engine can restrict the type of access via type of connection, ip, host, user, password, time of day, db, table, fields accessed, functions accessed, types of operations, etc. This is all built in - not something you have to code separately and hope you "got it right".

The "researchers" who claimed that an open port is, in and of itself, a security risk, need to realize that an open port is just that - an open port. It means nothing if you don't know how the machine is configured.

"It would be much nicer to have a nice system like PostgreSQL has, where you can assign various hosts to auth methods, but usernames are unique."

So, if you had a single user, but wanted different security depending on where they connect from (local or remote), you need two usernames? In MySQL it's simple and easy to set up that common scenario.

As for various auth methods, there are plans for authentication plugins to allow it, but as far as changing the core system, I would prefer to keep it as simple and easy as possible, with complexity provided through plugins. See here:

http://forge.mysql.com/wiki/PluggableAuthenticationSupport
http://forge.mysql.com/wiki/PluggableAuthorizationSupport

Cheers,
j

"It would be much nicer to have a nice system like PostgreSQL has, where you can assign various hosts to auth methods, but usernames are unique."

So, if you had a single user, but wanted different security depending on where they connect from (local or remote), you need two usernames? In MySQL it's simple and easy to set up that common scenario.

As for various auth methods, there are plans for authentication plugins to allow it, but as far as changing the core system, I would prefer to keep it as simple and easy as possible, with complexity provided through plugins. See here:

http://forge.mysql.com/wiki/PluggableAuthenticationSupport
http://forge.mysql.com/wiki/PluggableAuthorizationSupport

Cheers,
j

http://www.mysql.com/training/courses/database_design.html

(Bug submitted Feb 2005)

Can't be so hard. About every other database does it.

One of the things I've always felt is most lacking for Open Source databases is good client-side GUI tools to do ad-hoc queries, look at the database structure, assist in copying/importing/exporting data, etc. Microsoft has a pretty good tool in this area with either the SQL Enterprise Manager/Query Analyzer combo or SQL Server Management Studio.

MySQL on the other hand has a poorly-implemented, not-well-supported equivalent to Query Analyzer called MySQL Query Browser: http://www.mysql.com/products/tools/query-browser/ It's slow, crashes often (especially when called upon to list large datasets), and has tons and tons of usability flaws (the most glaring being the impossibility to select/copy the dataset to any other applications, and the failure to support standard keyboard shortcuts like Control/Command-A to Select All.)

It seems to me that MySQL Query Browser is treated, at best, as a second-class citizen in the MySQL world. Is that the case? If so, is it simply due to a lack of qualified developers for it, or is it part of a larger strategy to keep more resources working on the back-end?

In my opinion, MySQL could benefit greatly from having some really great (or at least passable!) client-side tools.

That is one advantage the For Profit Companies have, Management can get good developers to work on Code they don't think is 7337 or fun or interesting but needed to get the job done.

I am not suggesting that MySQL FULLTEXT is the end all, be all of indexes. I just pointed out that it existed.

Here is the missing link to tsearch2. It looks interesting.

Just so you know, you can override the > 50% stopwords. From the documentation:

Users who need to bypass the 50% limitation can use the boolean search mode;

And MySQL 5.1 has made it more flexible:

In MySQL 5.1, it is possible to write a plugin that replaces the built-in full-text parser. For details, see Section 28.2, "The MySQL Plugin Interface". For example parser plugin source code, see the plugin/fulltext directory of a MySQL source distribution.

I am not suggesting that MySQL FULLTEXT is the end all, be all of indexes. I just pointed out that it existed.

Here is the missing link to tsearch2. It looks interesting.

Just so you know, you can override the > 50% stopwords. From the documentation:

Users who need to bypass the 50% limitation can use the boolean search mode;

And MySQL 5.1 has made it more flexible:

In MySQL 5.1, it is possible to write a plugin that replaces the built-in full-text parser. For details, see Section 28.2, "The MySQL Plugin Interface". For example parser plugin source code, see the plugin/fulltext directory of a MySQL source distribution.

I know your just trying to be funny, but what you are describing already exists in MySQL. It's called FULLTEXT.

PCIe will likely give you performance more in-line with main memory (most implementations now are hitting 1-2 GB/s).

If I HAD a problem with it I wouldn't use it. I know this will shock you to the core, but, for what I use Microsoft products for, they serve me pretty well. My games work, I seldom need to reboot, I have 15 applications open, and the machine's not crapping itself.

I'm working on a Windows machine right now, and the most troublesome piece of software I use on it is fricking FIREFOX, and I am actually considering boycotting it...To the point that I've actually bothered to download the new version of Opera for the first time in god knows how long.

Right now I'm running Eclipse, Putty(x4), Navicat, Reflections, Dreamweaver, MS Management Console, MySQL Query Browser(x2), Outlook, Firefox, and Access 2003. Nothings causing me any problems, I'm on top of all my systems, and I'm satisfied...If I wasn't I'd be using something else.

Apparently though, I'm some kind of intellectual traitor for not being miserable, and not boycotting all these products that aren't making my life a living hell, just because a zealot thinks I should. And yes, if you decide that my using Windows software is symptomatic of the moral decline of the US you're undoubtably a zealot.

People like me, who are comfortable dealing with open and closed source software do more for OSS and the free software movement than all the hairy fanatics who equate closed source with all the evils of the world. If you can't even appreciate that there are legitimate reasons why people use closed source products instead of their OSS competitors, you are NEVER going to create a superior OSS product because you have absolutely no idea of what the POINT of the product actually IS.

MySQL: Because data corruption is no big deal.

Patently false!!! It just silently truncates data. That's not a bug, it's a feature!

Duh... I guess this dipshit (and everyone else here) does not comprehend the difference between a full text table index on the article bodies versus an actual "index" of topic titles, and the implication on search functionality.

I'm guessing this is the first time he has encountered the length of time it takes to create indices on text fields in a large db. You see, to get fast searches on huge amounts of text one must do a little work in advance.

Also I'd bet that the default offline wikipedia scripts define the table with indices, then imports the data, forcing the index to be rebuilt with every query (will take a painfully long time). I bet that a simple modification of the scripts to define the tables without indices, import the data then add the indices would speed it up considerably. (though index creation on large text databases will always take time no matter how you cut it)

A searchable zipped file of article titles? Whoopee fuckin doo.

RTFM assholes:
http://dev.mysql.com/doc/refman/4.1/en/indexes.htm l

Uhm... http://dev.mysql.com/doc/refman/5.0/en/innodb-and- mysql-replication.html

"MySQL replication works for InnoDB tables as it does for MyISAM tables. It is also possible to use replication in a way where the storage engine on the slave is not the same as the original storage engine on the master. For example, you can replicate modifications to an InnoDB table on the master to a MyISAM table on the slave."

Actually FLPR is related to the mascot for MySQL.

This is the next step on from creating a second-class citizen 'community' codebase.

MySQL.com have always tacked open source on as an afterthought.
Their contributor agreement is effectively
'thanks, your patch, copyright and patents belong to us now, but here's a free t-shirt for your trouble'.

http://forge.mysql.com/contribute/cla.php

I hope this makes some of the bazillion webapps
that couldn't be bothered to support other databases realise all their eggs are in a pretty ropey basket right now.

MySQL versions 5.0.38 to 5.0.45 have had such major bugs that they have rendered themselves useless for a huge range of applications. Applications that use dates, or ones that expect the database to *NOT* insert random NULL values in a group by query.

I mean, even the most basic test suite would have easily caught these.

Here are just a few of the major ones:
Bug #28336
Bug #28936

MySQL versions 5.0.38 to 5.0.45 have had such major bugs that they have rendered themselves useless for a huge range of applications. Applications that use dates, or ones that expect the database to *NOT* insert random NULL values in a group by query.

I mean, even the most basic test suite would have easily caught these.

Here are just a few of the major ones:
Bug #28336
Bug #28936