sorted by: recent | see : popular

Content Tagged with Announcements + MySQL

A lot of people have been waiting for this a long time - so I am very happy to announce that we will publish the first Alpha that runs natively on Linux end of September. We will release generic binaries and the 5.1 source tarball including everything that is needed to build yourself.

This will not be a feature-complete beta release yet, but we are trying to get the basic functionality working so everybody can start modeling right away. We spent most of the last few months working on updating the Back-End implementation to use the GRTv4 and to prepare our platform-independent mForms. I expect the actual Front-End port to make good progress.

Let me share two screenshots I just made on Ubuntu, our Linux distro of choice. The first one shows the MySQL Model page. The Sakila demo model has been loaded.

The second screenshot shows the EER Diagram. This first Alpha will still use the software rendering option but we are looking forward to enable the OpenGL pretty soon.

Keep monitoring the blog - we will publish new screenshots as we go.

Welcome to Proven Scaling’s new official home on the web. We’ve been meaning to set up a company blog for quite a while, but since we already have personal blogs, it kept getting pushed to the back burner. Finally, with much ado, it’s up!

A little about Proven Scaling and our history

Proven Scaling was founded by Jeremy Cole and Eric Bergen in May, 2006 in order to provide our skills in MySQL architecture, performance, reliability, and availability to a larger audience. Currently Proven Scaling consists of:

• Jeremy Cole — Jeremy left Yahoo! after 1.5 years, a few months ahead of Eric, to kickstart Proven Scaling in July, 2006. Previous to Yahoo!, Jeremy worked for MySQL AB for 4.5 years as tech writer, trainer, consultant, and occasional developer. Jeremy has a personal blog at jcole.us.
• Eric Bergen — Eric left his 1.5 years at Yahoo! to join Jeremy in September, 2006. Previous to Yahoo!, Eric was responsible for MySQL and related systems at a major domain registrar. Eric has a personal blog at ebergen.net
• Mike Griffiths — Based in London, UK, Mike joined Proven Scaling in November, 2007. Before joining Proven Scaling, Mike worked at Yahoo! for 7 years, responsible for MySQL in Europe, Asia and beyond. Mike has so far steadfastly refused to join the blogosphere, arguing that no-one’s really interested in his thoughts on sport, DIY, perl hacking, warm English beer and the other things which take up his leisure time.

A lot more than consulting…

At Proven Scaling we spend a lot time working on various software projects. Jeremy and Eric have been publishing their own patches to MySQL and other projects for many years. One of the primary reasons for forming a company together in the structure that we have is to ensure that we maintain the hardware resources, ability, and time available to work on these projects and provide them to the public in as quick and efficient manner as possible. In addition to continuing our previous work, Proven Scaling has been working on several new independent projects to solve problems in the MySQL space.

We needed to place to distribute that software along with other widely and not-so-widely available software packages, so we host a software mirror at mirror.provenscaling.com. This site hosts hard to find copies of various software packages we use every day, in addition to RedHat-friendly (and CentOS friendly) yum repositories for many packages. In fact, one of the reasons we are starting this blog is so that we have an official place to keep you updated as to the contents of our mirror site. As we update the mirror with new releases of existing software and entirely new software, we will post entries describing the updates.

What will we blog about?

You can get some idea of the topics you might see here from Jeremy and Eric’s MySQL posts on their personal blogs: MySQL on jcole.us and MySQL on ebergen.net.

In addition to the updates described above, some of the topics we are especially interested in writing about are:

• Announcements of new Proven Scaling software and new releases of our software
• New patches or ideas for patches to MySQL and other software
• Deep dissections of various parts of MySQL and InnoDB
• Knowledge gained from working with our customers, such as advice for real-world scenarios or unexpected situations
• Many more exciting ideas we’re working on, which we will share when they are ready!

Sounds good?

Go ahead and subscribe to our RSS feed, or bookmark this page. Keep an eye on the author names above, so that you know who’s writing.

I would like to say a big Thank-You to the community. It has been quite a ride this last year for my team and me, designing and coding MySQL Workbench, getting it to GA quality, presenting at the UC and constantly continue to improve quality since then. Now let’s look at the facts.

• I am happy to announce that we have reached more than 400.000 downloads of MySQL Workbench today, which is quite a lot for a highly specific tool in such a short time-frame (406690 at 18:25 GMT+1 to be exact).
• We have about as many downloads a day as the MySQL Server 5.1 server on Windows, also quite impressive I think for a little database design tool (I am only comparing Windows since Workbench is only available on Windows yet).
• The number of incoming bugs has been going down after each new release and we are now at a constantly low level. Nevertheless we are continuing our bug-fix releases while working on MySQL Workbench 5.1, the ports to Linux/Solaris and OS X.

Stay tuned for more good information.

After some glitches - mainly introduced by switching to the new source control system - we are presenting a new release of version 5.0 (built right out of our shiny new bazaar repository). This release has another 17 bugs fixed (along with some additional adjustments to improve usability). While we are already working in parallel at version 5.1 we are constantly fixing the remaining bugs in our present release version.

We are proud to announce that MySQL Workbench has reached GA (General Availability)
status and the final version - 5.0.19 - is available on our mirrors.

We managed to get another 32 bugs fixed since the last Release Candidate and hopefully there aren’t many still hidden in our code. We are planning to release a new Version of Workbench every three weeks so if new bugs are found and reported we’ll fix them and supply a improved build quickly.

Get a copy of our OSS Edition from Servers now and start designing your databases.
If you want all the time-saving features (including direct connection to DB, Validation of your models, …) you could invest 99 USD on the Standard Edition - please go to http://shop.mysql.com and get your license there! (Our web-shop is currently being prepared so Workbench will be available there at 4pm PST)

We have just officially released the WB 5.0 RC3 build and are planning the GA build to happen soon. One might ask, what is our criteria to call something GA? Well, it means that there must not be any known and verified P1 (crashing) and P2 (very serious bug with no workaround) bugs. Does it means that there are no bugs left or that we have implemented every feature request? No.

Therefore our efforts will not stop after the GA build. We still plan to get a new release out every 3rd week including all fixes and improvements that are necessary. This is a first list of things we are planning to release in a future GA release.

• Bug fixes
  Most important are bug fixes of course. Please keep reporting bugs, you did a great job in the past - and if you do so, we will keep closing those bug reports as fast as we can.

• Enable connection-end points dragging/reordering
  This has remained one major point of complaint, but we cannot commit the code in time for the GA release as this has to be tested much more.
• Canvas speed optimizations
  While we have made improvements here there is still a lot to work on, especially for large diagrams. My current advice is to break the huge diagrams down into smaller ones so that they become easier to manage. To have many different diagrams in one model is one core feature of Workbench and I would like to encourage people to really make use of that (even if larger models can be displayed faster in the future).
• More DBDoc templates
  We only ship a small number of reporting templates in SE yet. This is going to change. If you have special requirements or ideas how the reports should look like please post your ideas on the forums.
• Online repository of model snippets
  When you do a lot of database modeling you might have noticed that you reuse the same structures quite a lot. We want to offer a collection of diagram snippets that will allow you quickly add typical structures to your model.
• Online repository of plugins
  Vlad is giving a tutorial at the MySQL Users Conference on how to write plugins for Workbench. We want to offer an online repository for those as well. Sergei is currently working on a Download-Wizard to make downloading those extensions really easy.

As you can see, we have lots of plans for the WB 5.0 GA release and this does not even touch the things we will be working on for the WB 5.1 tree.

There are great times ahead of this project!

Now that the GA (General Availability) release of MySQL Workbench is coming up it is a good point in time to discuss what the commercial Standard Edition subscription will be all about and what will be covered by it. While I am not a lawyer I will try to explain the ideas behind the concept. Please make sure to read the subscription details when you get it.

Key points:

• USD 99
• Single seat license (license packs for a large number of seats (>30) possible)
• Software never expires
• Includes all updates of Standard Edition for a full year
• Binaries always accessible via MySQL site

The Basics

After the official launch you will be able to buy subscriptions in the MySQL Online Shop. Apart from payment with standard credit cards it has been updated to also allow for PayPal payment. A subscription will cost USD 99 (good for people in Euro countries, I know) and is valid for a single seat. If you are a bigger shop and need several installations, the appropriate number of subscriptions need to be acquired. For a real large number of subscriptions, e.g. 30 or more, a sales representative should be contacted.

When you have completed your purchase you will get an account on the MySQL Eventum server. After logging in you can access the binaries. You will have access to the MySQL Customer Portal for the duration of your subscription term.

Your subscription gives you access to all upgrades/updates/fixes of MySQL Workbench Standard Edition that are released during your subscription term. So there is no reason to keep waiting for future releases. The updates can be performed with the handy auto-update feature that we built inside WB. We plan to keep the frequent 2-3 week release cycle that we currently have in place.

Mike

p.s.: One personal comment for people with a workstation and a laptop. While the license is a per seat license I can see nothing wrong in using the same license on the workstation installation as well as on the laptop installation - as nobody is working on both devices at the same time usually.

Shortly after getting RC1 out we have now released RC2. We fixed a few issues that were reported after RC1 was out, thanks for that! In addition to that we included a first version of the GRT Scripting IDE that will play a key role for the MySQL Workbench community in the future.

The GRT Scripting IDE allows to easily create scripts, libraries and modules that extend the core Workbench functionality. We will add detailed documentation and tutorials that will get people started. Vlad is hosting a tutorial on this topic at the upcoming MySQL Users Conference as well.

We also plan to create an online repository where people can share their Workbench extensions - think Firefox Extensions - but also including things like diagram-snippets, sample models and much more.

Please give RC2 a try and report your findings on the forums or via the bug system.

MySQL Workbench Forums

Thanks!

p.s. “GRT” stands for “Generic Runtime”, the scripting environment we have originally created for the MySQL Migration Toolkit but improved since back then. It allows to combine and add modules in many different languages like Lua, Python, Java, C++, …

We uploaded a updated beta release 5.0.14a to our mirrors yesterday. There was a small issue (with not so small effects) where some users were unable to open files created with earlier versions of MySQL Workbench. Please fetch this update to avoid this problem.

We are about to release the next Beta version of MySQL Workbench. There are no new additions like in the last release. This will strictly be a bug-fix build. Apart from several smaller fixes this build will see an improved software rendering performance. Alfredo has blogged about the changes in his last post. And the changes are really paying off. Tax tested it on several machines and found the speed to be acceptable even on older machines.

The slow and flickering software rendering has been one of the major points of complain (except from the yet missing Linux and OS X versions that will be released later this year). Now that this is out of the way we are marching towards the RC level, fast.

If there are no new obstacles the release build will happen later today. Markus from the web team will get online on Saturday or early Sunday to update the download pages. Then we will send out the announce emails asap.

We finally got WB 5.0.12 released. It was a bit complicated to get it out because everybody was on his way to the MySQL All Company Meeting here in Orlando, Fl, and with all the meetings going on. 5.0.12 is a next important step to get closer to RC. We did not fix as many bugs as for the last releases - partly caused by the vacations around X-Mas but as well because the number of serious issues is going down. There is still a lot to be done though but the light at the end of the tunnel is clearly visible already.

Btw., if somebody did not get the news yet (which I don’t think is possible), MySQL has been aquired by Sun. It is the biggest topic here at the All Company Meeting and I think it was the best thing that could happen for MySQL as a product and for the community. What it means for the MySQL Workbench project for the moment is, that nothing will change. We will continue our road to GA as planned and are currently putting together the feature set for the WB 5.1 release. But I think there might be some very good things happening for the community in the future.

Check the forum announcement for more information installation instructions and compatibility notes.

Please report any issues and/or feedback at the Virtual Appliances Discussion Forums (forums.virtualappliances.net).

LAMP

http://virtualappliances.net/download/archive/VirtualAppliancesLAMP-xen-1.0.113.tar.bz2
http://virtualappliances.net/download/archive/VirtualAppliancesLAMP-xen-1.0.113.zip

Cacti

http://virtualappliances.net/download/archive/VirtualAppliancesCacti-xen-1.0.112.tar.bz2
http://virtualappliances.net/download/archive/VirtualAppliancesCacti-xen-1.0.112.zip

PostgreSQL

http://virtualappliances.net/download/archive/VirtualAppliancesPostgreSQL-xen-1.0.077.tar.bz2
http://virtualappliances.net/download/archive/VirtualAppliancesPostgreSQL-xen-1.0.077.zip

MySQL

http://virtualappliances.net/download/archive/VirtualAppliancesMySQL-xen-1.0.074.tar.bz2
http://virtualappliances.net/download/archive/VirtualAppliancesMySQL-xen-1.0.074.zip

Thanks for using Virtual Appliances!

Our new LAMP Virtual Appliance provides turnkey Apache HTTP Server, PHP, Perl, Python, and MySQL in one easy to use 65MB download.

This appliance features optional use of virtual hard disks for MySQL and web content.  Uniquely, this Virtual Appliance shares the web content via CIFS/Windows Networking for extremely easy to use content publication and mnagement.  Many popular web applications can be deployed using this appliance.

As usual, free to download and use HERE.  Paid support options are available.

Hot from the Virtual Appliance Turkey Fryer, build 74 of the PostgreSQL Virtual Appliance is available for download here

This appliance features automated use of Virtual Hard disks to allow the nano sized appliance to access any size storage for its database.

This appliance provides an upgrade to PostgreSQL 8.1.4.

Enjoy.

Patrick released a new version of the perl MySQL connector. This .pm was my introduction to the mysql world, way back in the day. If you can program your way out of a perl brown paper bag and you haven’t used this tool yet, I recommend you write a hello world program to get familiar with it. Good stuff.

Dear DBD::mysql users,

This announcement comes a few days late, but DBD::mysql version 3.0004
(stable, production) and 3.0004_1 (dev) have been released!

Version 3.0004 is the production version with server-side prepare
statements turned off by default, and 3.0004_1 is the development
version with server-side prepare statements turned on by default.

The changes in 3.0004, as listed in the changelog:
  * Fix dbd_st_finish which closed the handle prematurely (Martin Evans)
  * Compile issues (Martin Evans)
  * Fix to dbd_bind_ph to deal with numbers (ints, floats) correctly
    (Alexey Stroganov)
  * Test changes - bind_param 41 and 42

The changes to 3.0004_1 as listed in the changelog:

* Fix dbd_st_finish which closed the handle prematurely (Martin Evans)
  * Compile issues (Martin Evans)
  * Small change to get utf8 data returned. One still has to:
      $dbh->do("set character set utf8");
      $dbh->do("set names utf8");

    to get utf8 back and even then you only get it back if the
    column is defined as utf8 in mysql.
  * Fix to dbd_bind_ph to deal with numbers (ints, floats) correctly
    (Alexey Stroganov)
  * Test changes - bind_param 41 and 42
  * Turned off 70takeimp test

Note: to turn on server-side prepared statements, simply append
";mysql_server_prepare=1" to the connect string or via the driver
handle. Please refer to documentation for further details.

Notes:

* The development (3.0004_1) version supports multiple result sets from
stored procedures. Documentation and sample code (in the ./eg dir) is
included on how to use multiple result sets. Also, the perldoc has
information on multiple result sets.

* To turn off server-side prepare statements to have emulated prepared
statements, append ";mysql_emulated_prepare=0" in the connect string or
via the driver handle.

*As listed in the second changelog, this code is now much better at
handling SQL statements that aren't supported in the prepared statement
C API, and silently deals with determining whether or not to use the
prepared statement calls.

I really appreciate the help of Martin Evans, Alexey Stroganov, Henri
Asseily, as well as the rest of the community in helping by giving
patches and feedback about various issues with the driver. Thank you!

NOTICE: Very soon, perhaps in a release or so, I intend to stabilise the
dev release and make that the production release. This means that server
side prepared statements will be turned on by default. I intend to test
this thoroughly prior to making the switch, so that users don't have any
problems when upgrading, when the time comes. This prepared statement
API is only available with MySQL server versions 4.1 and above, so if
you're using an older version, you won't notice anything. Though, be
assured that even for the driver emulated handling of prepared
statements, I will continue to make sure the code is improved.

As the community, one think you can do if you are interested in helping
is to turn on server side prepare statements in 3.0004, or try the
development driver, 3.0004_1 to see if there are any problems. I've
tested the code as much as I can, but I know nothing tests code like
1000s of developers thinking of unique ways of using the driver that I
never could have imagined. If you find a bug, please report it to me, or
at http://bugs.mysql.com. I'll fix that bug and add test coverage for it.

Coveati: Please make sure you don't use a threaded Perl with this driver
on Solaris.

Again, if anyone has any problems or questions with the driver, please
feel free to email me, or especially post to dbi-users@perl.org , and if
you find bugs, please report them to http://bugs.mysql.com

These versions for this module can be found at CPAN:

http://search.cpan.org/dist/DBD-mysql/

The files:

file: $CPAN/authors/id/C/CA/CAPTTOFU/DBD-mysql-3.0004.tar.gz
size: 113043 bytes
md5: 5d328b9fdaf899eba6d72258242ad0a0

file: $CPAN/authors/id/C/CA/CAPTTOFU/DBD-mysql-3.0004_1.tar.gz
size: 110175 bytes
md5: 4dfbd956417f5b036ab55defb8fdfac7

Kind regards,

Patrick Galbraith

© cjcollier for C.J.'s WordPress of studlyness, 2006. | Permalink | No comment

Add to del.icio.us

Search blogs linking this post with Technorati

Want more on these topics ? Browse the archive of posts filed under work, mysql, perl, SQL, release announcements, DBD::mysql.