Bug #2561 Please clarify the behavior of TIMESTAMP with replication

• Submitted: 29 Jan 2004 12:01
• Modified: 31 Jan 2004 11:26
• Reporter: [ name withheld ]
• Status: Won't fix
• Category: MySQL Server: Documentation
• Severity: S3 (Non-critical)
• Version: N/A
• OS: N/A
• CPU Architecture: Any

[29 Jan 2004 12:01] [ name withheld ]

Description:
In section 6.8 (Replication FAQ) the following line appears:

"Indeed, when the slave SQL thread executes an event read from the master, this thread modifies its own time to the event's timestamp (this is why TIMESTAMP is well replicated)."

It would be useful to include a short section covering that in section 11.2.2 (The DATETIME, DATE, and TIMESTAMP Types) explaining how TIMESTAMP is handled in a replicated environment.

Also in 11.2.2 on the website there is an extraneous < p > tag which makes 

"TIMESTAMP properties as of MySQL 4.1 when not running in

MAXDB mode"

look funny.

How to repeat:
N/A

Suggested fix:
N/A

[31 Jan 2004 11:26] Paul DuBois

The problem with the extraneous tag in the
section heading has been fixed. Thanks for
noticing this.

However, TIMESTAMP replication already
is covered in the replication chapter; it's
not clear why the column types chapter should
cover it. There is no mention of replication
anywhere in that chapter.