New answers tagged mysql-5.1
To change innodb_log_file_size do following Stop MySQL gracefully. Check the error log and make sure it was "Normal shutdown", no crashes, no errors etc. Move existing ib_logfile* to safe place. You will need them if you want to roll back Change innodb_log_file_size in my.cnf to the new value Start MySQL. InnoDB will notice there are no ib_logfile* and ...
I hope this ll give you what u r looking for. with rnCTE AS ( SELECT *, rn = ROW_NUMBER() OVER (ORDER BY (SELECT 0)) FROM candidate ) DELETE FROM rnCTE WHERE rn = 2 Or DELETE rw FROM ( SELECT rn = ROW_NUMBER() OVER (ORDER BY (SELECT 0)) FROM candidate ) AS rw WHERE rw.rn = 2 For My Sql delete from candidate ...
Use a binary distribution (or compile from source) and then install using your system specific my.cnf (see below for mine). pol@Pol-laptop:~/Downloads/mysql/src/inst5.6$ ./scripts/mysql_install_db --defaults-file=/home/pol/Downloads/mysql/src/my.cnf Then, when you kick off your 5.1 instance, specify the my.cnf in the --defaults-file option to the mysqld ...
Delete using row id . Each row will have a unique id. so delete the row by using this unique id.
In order to perform an upgrade with (almost) no downtime, you need to add some extra infrastructure for high availability. The most common way to perform that is with the help of MySQL built-in replication: Setup a slave with a clone of the data of the original master. It is technically possible to setup a master-slave replication within the same node by ...
It's all here. What's wrong with mysqldump options | mysql localhost_name -u me -pmy_password (with valid options for your particular setup)? Check here for a sample. I don't know for sure, but Navicat is, in all likelihood doing something similar in the background. This is possibly better.
Top 50 recent answers are included