RSS News Sources

Paul M Foster

dealTek

hey i want to know how can i connect mysql(phpmyadmin) with my website like shows stats names etc

Subject says its all, this is of course, very good news coming out of the Red Hat Summit. Looking forward to Red Hat Enterprise Linux 7. And of course, CentOS 7 and the other builds that follow. Thank you Red Hat!

MariaDB replaces MySQL in RHEL 7. Glad to see that. #rhsummit

— Major Hayden (@majorhayden) June 12, 2013

at #rhsummit , rhel7 will come without mysql as it will be replaced with mariaDB; which is mysql api compatible. it will include mongodb too

— John Fulton (@fultonj) June 12, 2013

Related posts:

1. MariaDB in Red Hat Software Collections
2. Biggest MySQL related news in the last 24 hours
3. SkySQL Solutions Day, FOSDEM MySQL activity

PlanetMySQL Voting: Vote UP / Vote DOWN

I do not recall seeing an announcement about it, but I went looking for the videos today and lo and behold, they were up! Forgive me if I missed a post about it….but if you also missed it, here they are:

2013 SkySQL and MariaDB Solutions Day for the MySQL Database

PlanetMySQL Voting: Vote UP / Vote DOWN

Trying to get into Manage Import / Export in the WOrkbench but getting an error

Cannot Open Administrator
The selected server instance does not have a MySQL server connection assigned and cannot be opened.

How else can I export the two databases and tables

Jason P.

So MariaDB 10.0.3 Alpha is out. Download it and remember to provide feedback.

When you run SHOW ENGINES by default, you don’t get CassandraSE or the CONNECT engine. Make sure you do a yum install MariaDB-cassandra-engine and a yum install MariaDB-connect-engine. 

You will run into conflicts if you had an older MariaDB-CassandraSE engine (so yum remove MariaDB-CassandraSE).

Once you’ve got the packages installed, you can either install the plugin or just restart mysqld.

Happy testing!

Related posts:

1. Using MariaDB on CentOS 6
2. Plugins & Storage Engines Summit for MySQL/MariaDB
3. Testing Fedora 19

PlanetMySQL Voting: Vote UP / Vote DOWN

20 years ago I started programming with Clipper and dBase files, I've had some education on SQL over the years but never developed with it. Now I've decided MySql is the way to go, but can't quite decide on Java or PHP? I'm used to the old ways and can't quite wrap my head around how to access, present, and report on the data. I think the database part of an application will be easy for me, please give me some "opinions" on the rest of building an application.

Thanks

Fred.

Jason P.

Upgrading from MySQL 5.5 to MySQL 5.6 is a fairly straightforward process. However, the move to version 5.6 does bring with it some new varaibles with which to work.

One of the recent innovations (pioneered by Percona in Percona Server 5.5 if I recall correctly) is the ability to "dump" the innodb buffer pool***. This can be done any time MySQL is running and can be configured to be executed during MySQL shutdown. One reason to do this is to have a server "pre-warmed" when you perform a server restart. Why this is important is that during server operation the innodb buffer pool will fill up. Typically the server will operate much better when this buffer pool is full instead of being empty or paritally full because the return of data from the buffer pool is much faster than returning data from disk. 

There are four important variables with each having a value of 'ON' or 'OFF'.

innodb_buffer_pool_dump_at_shutdown innodb_buffer_pool_load_at_startup              innodb_buffer_pool_load_now  innodb_buffer_pool_load_abort
The innodb_buffer_pool_load_at_start variable must be set from the configuration file (and consequently requires a MySQL restart) while all others are dynamic and can be set from the command line. While these are mostly self-explanatory let's take the time to explore each briefly.

• innodb_buffer_pool_dump_at_shutdown: as part of the MySQL shutdown process the buffer pool is dumped when this is set to 'ON'
• innodb_buffer_pool_load_at_startup: during startup of MySQL the innodb buffer pool is preloaded when this is set to 'ON' 
• innodb_buffer_pool_load_now: when set to 'ON' it initiates an immediate load of the innodb buffer pool
• innodb_buffer_pool_load_abort: when set to 'ON' it stops the load of the innodb buffer pool

In my minimal my.cnf configuration file for MySQL 5.6 I set innodb_buffer_pool_dump_at_shutdown and innodb_buffer_pool_load_at_startup to be 'ON'. This means that whenever I shut down and restart MySQL the buffer pools is automatically saved and then reloaded.

I will point out one important status variable - innodb_buffer_pool_load_status. This can be used to monitor the progress of the load of a innodb buffer pool. If it takes too long, or causes other issues, you can abort the buffer pool load by setting innodb_buffer_pool_load_abort to 'ON'. Here is an example showing a completed load:

 

mysql> SHOW GLOBAL STATUS LIKE 'innodb_buffer_pool_load_status'\G

*************************** 1. row ***************************

Variable_name: Innodb_buffer_pool_load_status

        Value: Buffer pool(s) load completed at 130612 11:06:21

1 row in set (0.00 sec)

 

mysql> 

 

 *** For the technical purist -- I realize the innodb buffer pool itself is not dumped. It really is a list of the innodb pages that will need to be read into the innodb buffer pool in order to restore it. However, much of the literature calls it "dumping the buffer pool", and I prefer to use that terminology as well. It might be more proper to say "dumping the list of ids of the pages in the innodb buffer pool in LRU order" but that is tough to write or even say!! 

PlanetMySQL Voting: Vote UP / Vote DOWN

Recently a several releases of MySQL Server were announced to our mailing lists. Do not miss following news:

• Announced releases:
  • Jun 6, 2013 - MySQL Server 5.1.70
  • Jun 6, 2013 - MySQL Server 5.5.32
  • Jun 6, 2013 - MySQL Server 5.6.12
• More can be found at: http://dev.mysql.com/ or http://www.mysql.com/

PlanetMySQL Voting: Vote UP / Vote DOWN

Rafnews

Hello Guys,
I had to unistall and now reinstall mysql connector 6.6.5

However for a couple of weeks of pure headache, I cant seem to reinstall it again.

1. In the event viewer, it said.

Detection of product '{1AAD0C51-CE9E-4ECD-BB2D-6981472569B1}', feature 'Core.Feature' failed during request for component '{34B6C828-355D-405F-82BC-F18BBC13871D}'

2. So I searched the registry and noticed I found the first Unique ID in 3 places, but notably under

... >> Windows Uninstal >> {1AAD0C51-CE9E-4ECD-BB2D-6981472569B1}

With values Display name MYsql connector 6.6.5 ( And loads other values )


Do I delete the registry entries ? I hope it would not affect my server, as Its important I get the mysql connector up and running

Or is there a registry clean up for this ?


many thanks
Ehi

In my database i have tables:

postaje (id (INT A_I), ime_postaje (VARCHAR), latitude (DOUBLE), longitude (Double))

proge (ID (INT A_I), ime (VARCHAR))

postaje_proge (ID (INT A_I), ID_postaje (INT), ID_proge (INT), stevilo (INT))

`postaje` are points (bus stops) on map with longitude and latitude, `proge` are roads that contains that points and `postaje_proge` is connection between points and roads (that we know on what roads stations are. `stevilo` is index of point on road...)
For example we have in `postaje` IDs from 1 to 9. in `proge` IDs 1 (ime aka name of road A) and 2 (B). So in `postaje_proge` we get:

[ID, ID_postaje, ID_proge, stevilo ]
[0, 1, 1, 1]
[1, 2, 1, 2]
[2, 3, 1, 3]
[3, 4, 1, 4]
[4, 5, 1, 5]
[5, 6, 2, 1]
[6, 7, 2, 2]
[7, 2, 2, 3]
[8, 3, 2, 4]
[9, 8, 2, 5]
[10, 9, 2, 6]

Now I would like to get Result that returns all points between 1 and 9 in a correct order (so IDs `postaje` should be this: 1, 2, 3, 8, 9 ). My English is not really good but I hope you will understand what I wanna do :D

Picture of what i wanna do:
http://shrani.si/f/l/NZ/1WTznZDw/iskanje.png

Many experts are recommending this amazing supplement that has helped many people all around the world; do you want to know about that? That is Triminex Green Coffee Bean . This is the fastest fat burner till date and thus can help you shed excess pounds faster. So if you have been struggling with lots of calories and want to get rid of that desperately then this is the right product for you. Not only fat burning but the Triminex Green Coffee Bean helps in managing many healthy functions, wanna know about them? Read on…

http://triminexgreencoffee.net/

We’re less than a week away from Percona MySQL University at Portland, Oregon next Monday, June 17. The latest in a series of FREE one-day educational events, we are pleased to feature 10 technical talks by members of Team Percona as well as local members of the MySQL Community:

• Vadim Tkachenko, Percona co-Founder and CTO, will talk about Percona XtraDB Cluster, Percona Xtrabackup and Performance and Improvements and new Features in MySQL 5.6
• Garrick Peterson, a member of Percona’s RemoteDBA team, will talk about MHA for MySQL High Availability in the Cloud
• Matt Yonkovit, our VP of Consulting, will explain how to work with BigData effectively
• Justin Swanhart, our Senior MySQL Instructor, will continue the topic of BigData with a talk titled, “Conquering BigData with MySQL and Shard Query“
• Daniel Nichter, lead of the Percona Toolkit development team, will survey Percona Toolkit Command Line Tools – as well as go into more detail about using pt-table-checksum tool to verify replication integrity
• And finally, Andrew Ferlitsch will share with how MySQL can be used to provide access to government data.

The daylong event will be held at Portland State University’s Smith Memorial Student Union, located at 1825 SW Broadway, Suite 327/8/9 Portland, Oregon 97201. Afterward, we’ll have a networking reception at the famed Paddy’s Bar and Grill sponsored by Tag1 Consulting featuring great networking possibilities and free drinks for event attendees.

If you’re in the Portland area and work with MySQL, then this is an event you can’t afford to miss…   So register now!

Please also join the Portland MySQL Meetup group for more MySQL-focused events in Portland

If you love the ideal of Percona MySQL University and would like us to bring the event to your city, please let us know!

The post Percona MySQL University @Portland next Monday! appeared first on MySQL Performance Blog.

PlanetMySQL Voting: Vote UP / Vote DOWN

PECL/mysqlnd_ms is client-side load balancing driver plugin for PHP MySQL that aims to increase distribution transparency when using any MySQL based cluster: failover, read-write splitting, abstraction on consistency (e.g. read-your-writes), partitioning/sharding support, … it’s all there. Until a few minutes ago, we had no special handling of transient errors. Sometimes a database server replies “come back in a bit and retry, no need to fail over yet”. And, that’s what the client shall do before giving up. PECL/mysqlnd_ms 1.6 (development version) is capable of hiding the retry loop, which makes it easier to use any existing PHP MySQL application with a cluster of MySQL servers.

Transient (temporary) errors are rarely observed with MySQL Replication but can be seen with MySQL Cluster. MySQL Cluster is an eager (synchronous) update anywhere (multi-master) cluster: all replicas accept reads and writes, replication is synchronous. See also the slide deck DIY: A distributed database cluster, or: MySQL Cluster for a brief introduction in distributed database theory relevant to MySQL users (presentation from the International PHP Conference 2013 Spring Edition).

Transient errors

MySQL Cluster scales well for write loads because it features transparent sharding (see slides). It automatically partitions data over multiple replicas. Over the time, for example, when adding replicas to the cluster, data may b redistributed. Rebalancing is an online operation, it does not lock out clients. Thus, you may observe a temporary error such as:

ERROR 1297 (HY000): Got temporary error 1204 'Temporary failure, distribution changed' from NDBCLUSTER

There may be other causes for temporary errors as well. In any case, its safe to ignore a 1297/HY000 and retry the command.

The latest versions of MySQL Cluster feature an implicit retry loop before returning the error to the client, if it is believed that your command is not time critical. Means, Cluster resends the command for you a couple of times with a short sleep period in between before returning control to the client to tell about the temporary problem. PECL/mysqlnd_ms 1.6 alpha got a similar loop: very basic and experimental. Here’s the idea.

Automatic retry loop

The dream of Andrey when he created PECL/mysqlnd_ms was to make using a cluster transparent. It should be possible to move an application from a single MySQL to a cluster of MySQL servers without code changes. Thus, as a first step, I have opted against offering a callback to decide on errors (like Connector/J does). Instead, it is possible to configure the retry loop in the config file.

The example config snippet instructs the driver plugin to start an implcitiy command retry loop when there is an error with the error code 1297. Its possible to configure a list of arbitrary error codes. Whenever 1297 happens, the command is retried for max_retries = 2 times. Between the retry attemps PECL/mysqlnd_ms 1.6 sleeps for usleep_retry = 100 milliseconds. In an ideal world, the temporary error is gone by the end of the wait loop. In the worst case of the error persisting, it is forwarded to whatever PHP API you use (mysqli, PDO_MySQL) leaving it to your application to deal with it.

{ "myapp": { [...] "transient_error": { "mysql_error_codes": [ 1297 ], "max_retries": 2, "usleep_retry": 100 } } }

Please, send us your feature requests: this is a "live report" from the hacking and nothing is set.

You can check whether an implicit retry loop has been performed by inspecting the statistics provided by PECL/mysqlnd_ms.

$stats = mysqlnd_ms_get_stats(); printf("Implicit retries to hide transient errors: %d", $stats['transient_error_retries']);

Failover vs. transient error

When talking to a cluster instead of a single machine there are two additional error conditions to handle:

• Permanent error: replica disappeared, forget about replica – for now: fail over to someone else…
• Transient error: replica says BRB/BBIAB, retry – replica is synchronizing, data distribution changes, …

PECL/mysqlnd_ms applies failover logic whenever it connects to a replica. This can happen – due to lazy connect – not only when a connect() function of any PHP MySQL API is called but also during query(). At the time of writing, the retry loop is not applied for a connect attempt.

The new 1.6 transient error logic handles error conditions on already established connections. At the time of writing, it only covers query() – its a safe bet to assume that we cover all commands before the feature is called stable. Work in process, comments are welcome.

Happy hacking!

@Ulf_Wendel

PS: The overdue 1.5 stable release is coming soon. We forgot about it, simple as that.

The post PHP: PECL/mysqlnd_ms 1.6 – automatic retry loop for transient errors appeared first on Ulf Wendel.

PlanetMySQL Voting: Vote UP / Vote DOWN

Hello All,

I am new to this MySQL, I am trying to install MySQL and going to setup replication.

my question is i am using

Ubuntu 12.20 -- OS and MySQL 5.5.31

Fedora 12 -- OS and MySQL 5.5.32

is it possible to set up replication between 2 different OS and different MySQL versions.

Kindly let me know proper solution.


Regards,
Hari

Yet another MySQL User Camp is here ... Last MySQL user camp was held on 22nd of March, 2013 and it went very well. Introduction of MySQL India Team followed by MySQL 5.6 Presentation was very well received by attendees.

Best part was informal discussion with MySQL enthusiasts (with donuts and juices in our plate ;-) ) who are keen to know more and more about MySQL. I got to meet people who were very interested in MySQL Performance Schema and were willing to know how to use it and what benefits it provides to users. And more importantly "How it works".

Looking at the attendees response, it was decided to have this "MySQL User Camp" in every 3 months. So here is the time, 19th June 2013, A Wednesday, we are having another MySQL User camp. And looking at curiosity of attendees last time, I am speaking about MySQL Performance Schema, area where I work in MySQL.

And there is more. A session about MySQL InnoDB storage Engine which is default storage engine in MySQL now (earlier MyISAM was MySQL default storage engine).

And ofcourse, all these followed by informal discussion over snacks. :)


Here is the link having detailed information about MySQL User Camp.
https://groups.google.com/forum/?fromgroups#!topic/bangalore-mysql-user-camp/gnqGPLKDB0s

So explore this opportunity to come and meet MySQL Developers and Users. Registration is free. Don't forget to send mail to register yourself.


See you all there ....
PlanetMySQL Voting: Vote UP / Vote DOWN