| Bug #14541 | NDB can not replicate tables that do not have a PK | ||
|---|---|---|---|
| Submitted: | 1 Nov 2005 12:28 | Modified: | 2 Mar 2006 10:23 | 
| Reporter: | Jonathan Miller | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S2 (Serious) | 
| Version: | 5.1 | OS: | Linux (Linux) | 
| Assigned to: | Martin Skold | CPU Architecture: | Any | 
   [1 Nov 2005 12:28]
   Jonathan Miller        
  
 
   [12 Dec 2005 9:29]
   Martin Skold        
  Pushed implementation of cluster replication with tables with no primary key to clone mysql-5.1-wl2325-v3, to be merged with mysql-5.1 clone once RBR is pushed to 5.1.
   [2 Mar 2006 10:23]
   Jon Stephens        
  Thank you for your bug report. This issue has already been fixed in the latest released version of that product, which you can download at http://www.mysql.com/downloads/ Additional info: Per Martin/IRC: Fix was applied in 5.1.7; documented same in 5.1.7 changelog; closed.
   [18 Oct 2006 9:05]
   Mitul Savani        
  I am also receiving the same in my replication error log: 061017 18:54:39 [ERROR] NDB Binlog: logging of table ./juriscape/lcarticlemas_log with BLOB attribute and no PK is not supported 061017 18:54:58 [ERROR] NDB Binlog: logging of table ./juriscape/lccomments with BLOB attribute and no PK is not supported 061017 18:55:28 [ERROR] NDB Binlog: logging of table ./juriscape/lcerrorlog with BLOB attribute and no PK is not supported [root@rhel4mysql1 mysql]# rpm -qa | grep MySQL perl-DBD-MySQL-2.9004-3.1 qt-MySQL-3.3.3-9.3 MySQL-python-1.0.0-1.RHEL4.1 MySQL-server-5.1.11-0.glibc23 MySQL-shared-5.1.11-0.glibc23 MySQL-devel-5.1.11-0.glibc23 MySQL-client-5.1.11-0.glibc23
