|
このページは大阪弁化フィルタによって翻訳生成されたんですわ。 |
English
| Showing entries 1 to 10 of 14672 | Next 10 Older Entries |
Look what arrived in the mail! MySQL 5.1 Release t-shirts!
The back - with all our names
We made something similar for the MySQL 5.0 release and 10th anniversary, and sold that. I don’t know if we have plans to sell the MySQL 5.1 t-shirts,
[Read more...]
Inside Zend Server is a series of blog posts which I intend to write on Zend Server (time permitted). As I pointed out in my previous post on Zend Server there are a lot of different constituencies that Zend Server applies to. In this post I will focus on developers and system administrators who are using Windows either for developing or running PHP–based Web applications.
[Read more...]To move data from Sql Server to MySQL, it is certainly possible to use tools that can make connections to both data stores and manipulate data that way, such as Access, Excel, or SSIS. Here I will introduce a process that does not need any special tools or data drivers. Instead, we can use the utilities and methods that come with a standard Sql Server and MySQL install to accomplish that task.
With this approach, it is assumed that matching tables already exist on MySQL. If not, they need to be created first.
This process is comprised of these steps: first bcp command will be generated based on Sql Server database meta data (sysobjects, think information_schema in MySQL); then the generated bcp commands will be executed; the resulting csv files can then be transferred to the MySQL server, optionally it is possible to compress them if the size is big; and finally
[Read more...]With the release of MySQL 5.1, many DBAs are going to be scheduling downtime to upgrade their MySQL Server. As with all upgrades between major version numbers, it requires one of two upgrade paths:
I’m here to present a third option. It requires minimal application downtime, and is reasonably simple to prepare for and perform.
First of all, you’re going to need a second server (which I’ll refer to as S2). It will act as a ’stand-in’, while the main server (which I’ll refer to as S1) is upgraded. Once S2 is ready to go, you can
[Read more...]If:
1. A table t1 is created in database test;
2. A login is granted select permission on t1;
3. t1 is dropped and then recreated.
Then that login would still be able to read the newly recreated table t1, even if t1 has totally different columns. The reason is that the table select privilege is stored in tables_priv in mysql database, and when t1 is dropped, that privilege will not be cleared in tables_priv.
Personally, I think this needs to be changed. In other words, when a drop table command is issued, not only the table needs to be dropped, this command should also go to tables_priv in mysql to remove that select permission. Not too sure how big a task that is, perhaps I should try to see if I can implement it myself, after I get comfortable with the source code and development process of MySQL.
My calendar for the upcoming months is already filling up with conferences, trade fairs and other events at which I'll speak about MySQL. Here's a quick overview:
Last time I demonstrated a case where stored procedures are slow. There were a few comments that I should include selects in the stored procedure to make the tests more realistic. From experience I already knew the answer so I didn稚 go into that level of detail, but since stored procedures are all about database access this is a reasonable comment.
This is a simple stored procedure that selects data and then summarizes it by customer. No one would actually write this as it is far too easy to use a SQL statement instead. Assume the logic is more complex and can稚 be done easily by the standard SQL techniques of case statements, temp tables, etc, and then this makes more sense.
The end result is this stored procedure takes 696 seconds to run.
[Read more...]
I'm just back from a little vacation in the winter-wonderland and had some time on the train to spend. Thanks to power-plugs the 8hrs were well spent and ended up in a first, rough cut of a lua-customizable, mysql-shell that is based on the internals of the MySQL Proxy.
Branch
MySQL 5.1 release t-shirt
$ bzr branch lp:~jan-kneschke/mysql-proxy/mysql-shell
if you are interested and want to follow the development.
Everyone already has a mysql-shell, the mysql program that comes with each MySQL installation.
I wanted to take its idea a bit further and make it customizable with our well-known Lua interface. Even if this ongoing work, it already does something useful:
$ mysql-client
(not connected)> .connect
root@127.0.0.1:3306 []> select 1;
{
["1"] = 1,
}
OK (warnings: 0, auto-commit: true)
root@127.0.0.1:3306Well… kinda… (and nobody make fun of me for using my MythTV box as a testing ground for SQL against MySQL).
myth@orpheus:~$ mysql -u root test Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 2496 Server version: 5.0.51a-3ubuntu5.4-log (Ubuntu) Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> create table t1 (a tinytext default 'fail'); ERROR 1101 (42000): BLOB/TEXT column 'a' can't have a default value mysql> create table t1 (a tinytext default ''); Query OK, 0 rows affected, 1 warning (0.07 sec) mysql> show warnings; +---------+------+-------------------------------------------------+ | Level | Code | Message | +---------+------+-------------------------------------------------+ | Warning | 1101 | BLOB/TEXT column 'a' can't have a default value | +---------+------+-------------------------------------------------+ 1 row in set (0.00 sec)
| Showing entries 1 to 10 of 14672 | Next 10 Older Entries |
