December 26
The official MySQL Lifecycle Policy calendar terminates the end of the Active Support Lifecycle for MySQL 4.1 at the end of this year. The product is then entering the Extended Support Lifecycle. Please click on the image and read "What is the difference between Active Lifecycle and Extended Lifecycle support?" to understand the implications of this.
April 25
(by Gerardo Narvaja)
We do run on all platforms supported by Microsoft, embedded platforms not tested. We do support all communication protocols supported by Windows. Minimum disk space: 200MB, basically enough to unpack, install and create a few test DBs. We do run on all filesystems supported by Windows, for tables larger than 4GB NTFS is necessary. We do support a lot of DB access frameworks: ODBC, .NET (1.1 or newer), JDBC (1.4.2 or larger to develop, 1.3.0 or newer to run).
Packages are named a bit differently than on Unix.
Continue reading "MySQL on Windows for DBAs"
March 16
Right now all of your MySQL Developers are busy at MySQL Devcon 2006 in Sorrento. Each day is bracketed in the early morning and evening by the ritual of "Showstopper Bugs review", wherein the remaining showstopper, P1 and P2 bugs are reviewed, verified, assigned and the progress on their elimination is being tracked.
So far we are seeing a lot of progress - long standing and neglected bugs are suddenly going very easily, because people here can see each other and just talk about the problems they are seeing.
So more Sorrento means less lemons for all of you!
March 15
I requested this urgently for 5.1 and Brian made it happen: An information_schema table called processlist. This is the table version of the "SHOW FULL PROCESSLIST" output, and it is very cool. Using this table, you can create SQL to dig the processlist, and write stored procedures that spot, log and handle long running queries.
Even better: With the new log formats in 5.1, you can access the logs as CSV engine based SQL tables as well, and join the processlist table against the general query log or other logs. This allows you plenty of easy session tracing and easy profiling.
Even better: With the processlist table and 5.1 new feature "events" you can create new threads, monitor their execution, and in case of problems forcibly terminate them using other events or procedures. Or you can write a stored procedure using DROP USER to delete a user, and KILL this users connections afterwards to make sure that guy has been kicked.
The possibilities are endless.
March 10
I had a customer using Debian 64 Bit binaries downloaded from MySQL, experiencing hangs. Symptoms have been: - INSERT hangs
- Replication hangs (SQL_Thread shown as running, but Exec counter not moving)
- Server cannot be shutdown, except with kill -9
This is Bug #8555, Debian Bug 314408, a problem with NPTL in libc6, version 2.3.2.ds1-22. Upgrading to a newer, UNSTABLE version of libc6 resolved the problem. The system is now running without problems at 1200 qps (4000 qps peak) in 64 Bit mode, using the MySQL AMD 64 bit download for 5.0.18.
December 29
As a service to the busy, here are SuSE 10.0 RPMs of 5.0.19 a/o 2005-12-27 — use the spec-file to roll your own from the sources. This is a QND build, no warranty given, no responsibility taken.
September 12
As a service to the busy, here are SuSE 9.3 RPMs of 5.0.13 a/o 2005-09-09 — use the spec-file to roll your own from the sources. This is a QND build, no warranty given, no responsibility taken.
September 09
The most recent MySQL server I used in a production environment was a 3.23, so in conjunction with reading the 5.0 sources, I saw fit to reread large parts of the documentation to see where updates had happened, fixes were applied, extensions added. Here are some random clippings from the docs that illustrate quirks, changes from MySQL 3.23 (other than those noted in 3.23->4.0, 4.0->4.1, 4.1->5.0 which we'll give a brief tour of at the end) and differences from the standard. If you recently read the docs, kindly walk on, there's nothing to see here. If being a MySQL admin is #96 on the list of who you are, stand by for some trivia.
August 31
Just out of curiosity, and partly prompted by the IDE-poll on mysql.com, I tried to import the mysql-5.0 folder into the "usual suspects" as far as linux-IDEs are concerned:
August 30
As a service to the busy, here are SuSE 9.3 RPMs of 5.0.12 a/o 2005-08-30 — use the spec-file to roll your own from the sources. This is a QND build, no warranty given, no responsibility taken.
August 09
As a service to the busy, here are MySQL Query-browser 1.1.12 and MySQL Administrator 1.0.22a RPMs (SuSE 9.3, MySQL 5).
These are builds from the MySQL download section, not the repository.
Update recommended especially for the Query-Browser; the UI was improved, and I no longer get a crash I used to get with the SuSE binary.
August 02
Wherein we'll touch upon the main points of getting, building, and installing MySQL software — the main files and URLs to look at to get the developers' version from the repository, to compile, install and package it — for those living on the bleeding edge who start from scratch, and can't wait …
Continue reading "Fast forward MySQL: getting, building, installing"
July 28
As a service to the busy, here are SuSE 9.3 RPMs of 5.0.11 a/o 2005-07-28 — use the spec-file to roll your own from the sources. This is a QND build, no warranty given, no responsibility taken.
|
Community (12)
Comments
Sun, 11.05.2008 06:34
In reply to "stuff with no nam es":very informative and succi nct. I am retired and need to learn to build a website [...]
Wed, 30.04.2008 14:08
what is the difference between MySql and PostgreSql?
Wed, 09.04.2008 21:46
What a random fortune, who kno ws what it means. My favorite random fortune cookie note rea ds "you will make a good [...]
Thu, 27.03.2008 19:17
Hi Kristian, I noticed a fe w things that are wrong with y our above article. Overall it is good however, so don [...]
Wed, 19.03.2008 15:01
Sorry, I should mention that t he create transaction simply i nvolves doing: content = Bl ogContent.new(params[:co [...]
Wed, 19.03.2008 14:51
I like to separate text and bl ob columns into their own mode ls and tables, storing and man aging the record content [...]
Wed, 27.02.2008 04:47
IMHO: Rails is being designed and primarily used by people w ith a dedicated DB. So the ide a of constraining in the [...]
Wed, 27.02.2008 04:33
Rails only uses transactions i f you ask it to. If you just d o a People.find(:all), it does a select * from people, [...]