linux-traipu team mailing list archive
-
linux-traipu team
-
Mailing list archive
-
Message #01094
[Bug 811341] Re: `sys_replication`.`applier_state` lacks default values for originating_server_uuid and originating_commit_id
Joe,
0 for commit_id seems right, but are you sure '' should be used for the
uuid? I would think that we would insert a value unique to the local
database, but I haven't reviewed that bit of code you (I think) added
yet.
--
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Drizzle.
https://bugs.launchpad.net/bugs/811341
Title:
`sys_replication`.`applier_state` lacks default values for
originating_server_uuid and originating_commit_id
Status in A Lightweight SQL Database for Cloud Infrastructure and Web Applications:
Confirmed
Bug description:
When the following runs:
INSERT INTO `sys_replication`.`applier_state` (`master_id`, `last_applied_commit_id`, `status`) VALUES (1,0 , 'STOPPED')
We get an error because there are no default values for
originating_server_uuid and originating_commit_id in the
sys_replication.applier_state table.
What should the defaults be?
To manage notifications about this bug go to:
https://bugs.launchpad.net/drizzle/+bug/811341/+subscriptions
References