Update just some of the fields

2013-06-17 Thread Sayyed Mohammad Emami Razavi
In MySQL when i execute full update query, all fields will be updated or
no? It means, which fields that have not been changed will not be updated?!

e.g.
current values for table named 'test', i want to update just desc:
id, name, desc
1, test1, test2

update test set name='test1', desc='test10' where id=1;

I use one framework that still does not implement update just changed
fields, i know that i can use this:

update test set desc='test10' where id=1;

any ideas?!


Re: SLAVE aware of binary log file switch?

2013-06-17 Thread Denis Jedig

Am 17.06.2013 13:11, schrieb Mihamina Rakotomandimby:


Say the binary log file (on the master) has reached its maximum
size, so that it has to switch to a +1 binary log file: does he
inform the SLAVE of that switch so that the SLAVE updates its
information about the MASTER status?


The master does not inform the slave via an immediate 
communication channel, but the slave knows how to keep up because 
the end of the binary log file contains continuation information 
- i.e. the name of the next log file to fetch.


Denis

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql



MySQL 5.6.11 Missing MySQL Client

2013-06-17 Thread Nick Khamis
Hello Everyone,

We installed mysql 5.6.11 from source without server, and was
wondering what happened to the mysql command?

/usr/local/mysql/bin/
innochecksummysql_waitpid   replace resolveip
my_print_defaults   perror  resolve_stack_dump


Kind Regards,

Nick.

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql



SLAVE aware of binary log file switch?

2013-06-17 Thread Mihamina Rakotomandimby

Hi all,

Given a MASTER and a SLAVE.

When launching the SLAVE, it knows about the binary log file used by the 
MASTER and the position in that log file.


Say the binary log file (on the master) has reached its maximum size, so 
that it has to switch to a +1 binary log file: does he inform the 
SLAVE of that switch so that the SLAVE updates its information about the 
MASTER status?


I'm readind the documentation 
http://dev.mysql.com/doc/refman/5.1/en/binary-log.html and dont see what 
is happening while slaving.


Thank you.

--
RMA.



Re: SLAVE aware of binary log file switch?

2013-06-17 Thread Mihamina Rakotomandimby

On 2013-06-17 14:43, Denis Jedig wrote:

Say the binary log file (on the master) has reached its maximum
size, so that it has to switch to a +1 binary log file: does he
inform the SLAVE of that switch so that the SLAVE updates its
information about the MASTER status?
The master does not inform the slave via an immediate communication 
channel, but the slave knows how to keep up because the end of the 
binary log file contains continuation information - i.e. the name of 
the next log file to fetch.


OK.

I'm sorry I was mislead by the output of:
[mihamina@prod-ebidual ~]$ echo SHOW SLAVE STATUS \G; | mysql -uroot 
-px | grep 'Slave_'
   Slave_IO_State: Waiting for master to send event -- 
this

 Slave_IO_Running: Yes
Slave_SQL_Running: Yes

--
RMA.



Re: Update just some of the fields

2013-06-17 Thread hsv
 2013/06/17 11:38 +0430, Sayyed Mohammad Emami Razavi 
update test set desc='test10' where id=1; 

_That_ is UPDATE! It is the only means of changing, but neither inserting nor 
deleting, a record.

The other fields are left the same.

MySQL also tracks whether it is an actual change; this is reflected in the 
client message
Rows matched: ?  Changed: ?  Warnings: ?
. The number after Changed: is the number of records where the new value 
really differs from the old.


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql



RE: SLAVE aware of binary log file switch?

2013-06-17 Thread Rick James
 Waiting for master to send event -- just means that nothing is being 
replicated at the moment.

The Yes+Yes says that things are running.

Seconds_behind_master = 0 says that the Slave is essentially caught up.  NULL 
means something is broken.  0 _may_ indicate a problem, or it may indicate a 
brief delay.

 -Original Message-
 From: Mihamina Rakotomandimby [mailto:miham...@rktmb.org]
 Sent: Monday, June 17, 2013 5:35 AM
 To: mysql@lists.mysql.com
 Subject: Re: SLAVE aware of binary log file switch?
 
 On 2013-06-17 14:43, Denis Jedig wrote:
  Say the binary log file (on the master) has reached its maximum size,
  so that it has to switch to a +1 binary log file: does he inform
  the SLAVE of that switch so that the SLAVE updates its information
  about the MASTER status?
  The master does not inform the slave via an immediate communication
  channel, but the slave knows how to keep up because the end of the
  binary log file contains continuation information - i.e. the name of
  the next log file to fetch.
 
 OK.
 
 I'm sorry I was mislead by the output of:
 [mihamina@prod-ebidual ~]$ echo SHOW SLAVE STATUS \G; | mysql -uroot -
 px | grep 'Slave_'
 Slave_IO_State: Waiting for master to send event --
 this
   Slave_IO_Running: Yes
  Slave_SQL_Running: Yes
 
 --
 RMA.