-
-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Alter table changes not replicated to destination postgres db most of the time. #123
Comments
Tested in my environment and the column is added correctly. |
Hi, Please find the details: Chameleon version: chameleon_configuration:
Output of start_replica with debug option (in this option output was printing regularly so have killed it(ctrl +c) ) and started start_replica normally to resume operations.
|
I suggest you to upgrade pgchameleon to the latest version 2.0.14 as some bugs and improvements have been done.
|
HI, This one is version on staging but in my production I am using version 2.0.14. And over there I sometimes face same issue. Moreover I have tried altering table in MAIL, gui and BD schema and faced issue in all three sometimes. Is there any issue in configuration file. |
Hi, Any other suggestions. |
I understand there is a problem but I will check it out when I have time. By the end of the week as I work on this project on free time. |
Hi, Sure, thanks for update. Will be waiting. |
Describe the bug
Whenever we alter our table at source MySQL, the newly added column is not replicated to PostgreSQL. And we get below error in "sch_chameleon.t_error_log" table : 42703 - column "seg_id" of relation "tbl_abc_xyz" does not exist.
To Reproduce
Assuming that we have replicated MySQL to PostgreSQL. Create table using below:
CREATE TABLE
tbl_abc_xyz
(ab1_id
int(11) DEFAULT NULL,ab2_id
int(11) NOT NULL AUTO_INCREMENT,ab3_name
varchar(500) DEFAULT NULL,ab4_ID
varchar(64) DEFAULT NULL,ab5_used
varchar(500) DEFAULT NULL,ab6_Count
int(11) DEFAULT NULL,ab7_Count
int(11) DEFAULT NULL,ab8_count
int(11) DEFAULT NULL,ab9_Time
timestamp NULL DEFAULT NULL,ab10_Time
timestamp NULL DEFAULT '0000-00-00 00:00:00',ab11_time
timestamp NULL DEFAULT '0000-00-00 00:00:00',ab12_Type
varchar(64) DEFAULT NULL,ab13
varchar(64) DEFAULT NULL,ab14_Type
varchar(64) DEFAULT NULL,ab15_type
int(11) DEFAULT NULL,ab16_time
timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',ab17
timestamp NULL DEFAULT NULL,ab18_user_id
int(11) DEFAULT NULL,ab19_category
varchar(64) DEFAULT NULL,ab20_path
text DEFAULT NULL,ab21_rate
int(11) DEFAULT NULL,ab22_count
int(11) DEFAULT NULL,ab23_count
int(11) DEFAULT NULL,ab24_name
varchar(128) DEFAULT NULL,ab25_count
int(11) DEFAULT NULL,ab26_path
text DEFAULT NULL,ab27_count
int(11) DEFAULT NULL,ab28_count
int(11) DEFAULT NULL,ab29_path
text DEFAULT NULL,ab30
varchar(64) DEFAULT NULL,ab31_id
varchar(64) DEFAULT NULL,ab32_name
varchar(256) DEFAULT NULL,ab33_count
int(11) DEFAULT NULL,ab34_file
varchar(2000) DEFAULT NULL,ab35_type
int(11) DEFAULT NULL,ab36_by
int(11) DEFAULT NULL,ab37_file
longtext DEFAULT NULL,ab38_sequence
varchar(500) DEFAULT NULL,ab39
varchar(500) DEFAULT NULL,ab40_count
int(11) DEFAULT NULL,ab41Flag
tinyint(1) DEFAULT NULL,ab42_path
text DEFAULT NULL,ab43_path
text DEFAULT NULL,ab44_path
text DEFAULT NULL,ab45_path
text DEFAULT NULL,ab46_count
bigint(20) DEFAULT NULL,ab47_number
bigint(20) DEFAULT NULL,ab48_path
text DEFAULT NULL,ab49_count
int(11) DEFAULT NULL,ab50_count
int(11) DEFAULT NULL,ab51_time
int(11) DEFAULT NULL,PRIMARY KEY (
ab2_id
));
And then try to Alter table using below command;
Alter table abc.tbl_abc_xyz add column seg_id int;
Expected behavior
Newly added column does not replicate to PostgreSQL DB always and we found below error in "sch_chameleon.t_error_log" table : 42703 - column "seg_id" of relation "tbl_abc_xyz" does not exist.
Environment:
OS: Cent OS Linux release 7.8.2003
Python: 3.6
MariaDB: 10.3.14(Source)
PostgreSQL: 12.2(Destination)
The text was updated successfully, but these errors were encountered: