MySQL to make use of Microsoft code
84744
The code, which was open-sourced in April, will be used for the administration tool that connects to the MySQL database.
355740
MySQL has laid out its software road map through 2009, including some code contributed by Google and security improvements that are due in MySQL 7.0.Earlier this year Google signed a Contributor License Agreement, which provides the legal framework under which MySQL can include code from another company in its database, MySQL co-founder and Vice President David Axmark said on Tuesday.Google is secretive about the distributed architecture underlying its services, but it&#39;s known to be one of MySQL&#39;s biggest users, running hundreds or even thousands of its databases worldwide.The search company has done a lot of work customizing MySQL to meet its special needs, which include better database replication, and tools to monitor a high volume of database instances, Axmark said in an interview at MySQL&#39;s user conference in Paris.MySQL will include some of those capabilities in future versions of its database, probably in point upgrades to MySQL 6.0, which is scheduled for general availability in late 2008, Axmark said.Google benefits because the add-ons become part of the official MySQL product and are included in big fixes and future upgrades. MySQL could benefit from some of Google&#39;s custom software -- although it requires considerable work by the database vendor.&quot;It takes time to analyze what&#39;s relevant for everyone, what&#39;s doable, and how can we work it into a new version,&quot; said Kaj Arno, MySQL vice president for community relations. &quot;There&#39;s huge potential, but there&#39;s also lots of work.&quot;Google develops the add-ons only for the operating system it uses, Linux, so MySQL will need to port, test, and document the additions for the 15 or so OSes it supports.The features in MySQL 6.0 are already fairly set, Axmark said, so the Google code won&#39;t appear before version 6.1, due in early 2009. Some Google code is already in the source code for MySQL 4.1, he said, but not in a supported MySQL product.The companies are in close contact, Axmark said. The Google engineer in charge of its MySQL deployments spent several days at MySQL&#39;s internal developer meeting in Heidelberg, Germany, last month. Google has also released source code for some MySQL tools it developed.At its developer event in Paris, MySQL laid out an unusually long roadmap stretching to MySQL 7.0, which will be generally available in late 2009 and focus on security improvements for enterprise users.&quot;Many of you have told us you want better security in the database, and we have listened,&quot; Robin Schumacher, MySQL director of product management, told developers.Many of the features are standard in more mature databases from IBM and Oracle, Schumacher acknowledged in an interview. MySQL positions itself as a low-cost alternative to those products, with less sophisticated features that are sufficient for most users, most of the time.Schumacher said version 7.0 will support role- and group-based security, which allows administrators to set privileges for groups of users centrally instead of individually. It will also have &quot;transparent data encryption&quot; built into the database, so developers don&#39;t have to include it at the application level.MySQL hopes the security features will win it financial, government and retail customers, some of whom add the capabilities themselves. &quot;If we get the door slammed in our face in an account, this is one of the reasons it happens,&quot; Schumacher said.In the nearer term, MySQL 5.1 is scheduled for general availability in the first quarter next year. Advances include table and index partitioning, which should boost data warehousing performance, and the option of row-based replication, which lets companies create more exact back-up replicas.The big change in 6.0 will be the availability of&#160;MySQL&#39;s storage engine, Falcon. The most popular storage engine for MySQL has historically been InnoDB, but two years ago Oracle acquired InnoDB&#39;s developer, Innobase. Oracle continued to license the software to MySQL, but MySQL wanted an alternative.Falcon will do crash recovery and roll-back operations faster than InnoDB because they are done from main memory, Schumacher said, but some InnoDB features, like foreign key support and full-text indexing, won&#39;t be supported until MySQL 6.1.6.1 is due to go into beta in mid-2008 and start to ship widely in 2009. Improvements include better prepared statements and server-side cursors, Schumacher said.Despite all the buzz a few years ago about native XML (Extensible Markup Language) support, Axmark said he&#39;s still waiting for a clear signal about what customers want. Until then it&#39;s not a big priority for MySQL, although there are some XML capabilities in 5.1, he said.
662628
Go directly to the back-end database to optimize query processing. Bill Pearson leads a hands-on introduction to implementing Pass-Through queries to MSSQL Server 2000 from an MS Access client.
557949
A tool to manage database changes and refactorings. All changes to a database are stored in XML files that are stored in version control with other source code. A graphical IDE is also available   LiquiBase 1.2 has been released. Major features include:      * Support for H2 database     * Support for InterSystems Cache` database     * Support for  change     * Improved error messages     * tag can contain a  tag     * Change log file references can be absolute     * SQL in  tag can be ; or 'go' delimited     * New clearCheckSums command in command line migrator     * Support for version 0.5 of the LiquiBase IDE and Eclipse Plugin  Many bugs have been fixed as well, including:      * Sybase support fixes     * Handle --defaultsFile correctly     * Handle command line parameters correctly on Windows systems     * Other bug fixes  Upgrading is simply a matter of replacing the liquibase.jar file. To take advantage of newer change log features, change your XSD declaration to:    Download LiquiBase 1.2 from:  http://www.liquibase.org/download.html
414274
Nice!  MySQL 4.1 final is now available   "MySQL AB, developer of the world's most popular open source database, today announced the general availability of MySQL 4.1. Certified by the company as production-ready for large-scale enterprise deployment, this significant upgrade to the MySQL database server features advanced querying capabilities through subqueries, faster and more secure client-server communication, new installation and configuration tools, and support for international character sets and geographic data. MySQL 4.1 can be downloaded now at http://dev.mysql.com/."  ""Our user community has been testing MySQL 4.1 for many months, and hundreds of businesses have already deployed  ...
250953
New from Codewalkers.com today: Take a look whether or not to migrate your Access data to MySQL and then how the migration can be done with the help of Navicat, a MySQL database administration GUI, in our newest tutorial.
434961
Ajax has taken the Web to a new level by offering an intuitive interactive model that rivals the desktop. To compete with desktop applications, you'll learn how to create database-enabled Ajax requests using PHP and MySQL. By Kris Hadlock. 1122
311831
For the last few days I've been using MySQLs ALTER and REPAIR table functionality and its caused tons of countless problems and a great deal of lost sleep.  The first problem I noticed was that for large tables ALTER TABLE was taking hours!  Lets say you have a 30G table.  Good luck altering it as the default MySQL configuration will probably take 100 or more hours.  In MySQLs defense there are a number of variables you can use to increase the performance of an ALTER but the problem is that the two major ones (myisam_max_extra_sort_file_size, and myisam_max_sort_file_size) can't be set at runtime (during an ALTER). If these are set too low MySQL will revert to a "Repair with keycache" strate ...
319638
In this new tutorial on PHPBuilder.com, Ken Lin demonstrates how to import some data from an MS Access database into the most recent version of MySQL (version 5).   In this article, I will discuss whether or not to migrate your MS Access data to MySQL. Then, I will cover about the considerations, planning, and preparations which should made before migrating your data.   He follows the (good) practice of plan first, shoot later when approaching the subject. He talks about the differences between the two systems, when to and not to make the import jump, and some steps to do to prepare things for the leap.   He choses the Navicat tool to make the transition, stepping through the process the import wizard will follow to make the push much easier than a manual import/export.
143834
Latest PEAR Releases:CodeGen_MySQL_Plugin 0.9.1devCodeGen_MySQL 0.9.1devVersionControl_SVN 0.3.1Net_LDAP 1.0.0RC4Testing_FIT 0.2.2Net_UserAgent_Detect 2.4.0Text_Diff 0.3.0DB 1.7.13PHP_CodeSniffer 0.9.0
723293
Edin Kadribasic has released the latest update for his Win32 builds in the PHP 4.4.x series - PHP 4.4.5-win32 with the MySQL 5.0.22 drivers.   There's a direct download here which contains two files. Drop these top files into your current install folder and you should be good to go (it will overwrite one file and insert another).   Previous versions can be found as tagged on his blog.
196418
Using the Visual Studio 2008 development platform with SQL Server 2008 will require a patch.
426872
On the Internet Super Hero blog, there's this new post giving examples of compiling the MySQL native driver (mysqlnd) with different versions of PHP - 5.2, 5.3 and 6.0.   A user comment made clear that we need to send out a quick status update on how to install / compile mysqlnd with PHP 5.2, 5.3 and 6.0 .   The instructions are only slightly different for each of the version, mainly in the version that's checked out from CVS. The PHP 5.2.x part, however, suggests that you go ahead and make the move to/wait for PHP 5.3 to use the extension. It's still in beta and (probably) won't be included in any of the 5.2.x branches.
190663
Joshua Eichorn points out an interesting project in a new post to his blog today - quercus.   I found an interesting project, quercus that compiles PHP to Java Bytecode allowing it to run ontop of the Java Resin Application Server. It has a couple neat features, one being PHP6 compatible unicode support, the other being easy integration between Java and PHP code.   He gave it a shot and notes that the performance seems decent and allows you to compensate for some of the differences in the PHP API it supports and what you're using via a Java class. According to their site:   Quercus is Caucho Technology's 100% Java implementation of PHP 5 released under the Open Source GPL license. Quercus comes with many PHP modules and extensions like PDF, PDO, MySQL, and JSON. Quercus allows for tight integration of Java services with PHP scripts, so using PHP with JMS or Grails is a quick and painless endeavor.   It includes several extensions too, including the JSON library, APC, MySQL and Oracle support, and PDF functionality. Check out their Getting Started guide, documentation, or their wiki for more information.
631446
Microsoft guru predicts Vista half as buggy &gt;&gt; Advertisement &lt;&lt;  ALERT: "How A Hacker Launches A Blind SQL Injection Attack Step-by-Step"!" - White Paper  Blind SQL Injection can deliver total control of your server to a hacker giving them the ability to read, write and manipulate all data stored in your backend systems! Download this *FREE* white paper from SPI Dynamics for a complete guide to protection! https://download.spidynamics.com/1/ad/bsq.asp?Campaign_ID=701600000004c29
291398
Padraic Brady has posted a guide he's written up to show other developers out there how to compile PHP for Windows (Vista) using the Visual C++ Express 2008 software.   Over the past week or so I've been figuring out how to compile PHP on Windows, specifically Windows Vista. It's been an interesting ride since I'm not very familiar with compiling on Windows to start with. [...] If you are using Windows Vista, or intend updating/using Visual C++ Express 2008, then my blog entry is largely another coat of sugar on top of Elizabeth's guide to clear up any difference between the two approaches.   He lists the software you'll need to make the compile work (including Virtual Clone Drive, WinRAR, VS 2008 Express and the .NET Framework SDK)  and then breaks it down into three steps - the installation of the development environment (and setup), downloading PHP/libraries to the environment and, of course, compiling the PHP instance to your specs (complete with command line calls to make it all happen).
339557
This toolkit contains essential command-line utilities for MySQL, such as a table checksum tool and query profiler. It provides missing features such as checking slaves for data consistency, with emphasis on quality and scriptability.   This release of MySQL Toolkit adds a new tool, fixes some minor bugs and adds new functionality (especially the ability to run as a daemon) to several of the tools.  Download:  http://sourceforge.net/project/showfiles.php?group_id=189154  Changelog for mysql-deadlock-logger:  2007-09-20: version 1.0.4     * Added --interval, --time, and --daemonize options, and signal handling.    * --askpass did not allow different passwords on --source and --dest.  Changelog for mysql-duplicate-key-checker:  2007-09-20: version 1.1.1     * Exit code wasn't always defined.  Changelog for mysql-query-profiler:  2007-09-20: version 1.1.5     * Documentation didn't specify how queries in FILE are separated.  Changelog for mysql-slave-delay:  2007-09-20: version 1.0.1     * Added a --daemonize option to detach from the shell and run in the background.  Changelog for mysql-slave-restart:  2007-09-20: version 1.0.1     * Added a --daemonize option to detach from the shell and run in the background.  Changelog for mysql-table-checksum:  2007-09-20: version 1.1.15     * The CHECKSUM strategy was always disabled.  Changelog for mysql-visual-explain:  2007-09-20: version 1.0.3     * filesort wasn't applied to the first non-constant table.