Hello, Andrew sir: Completely missed that. Thanks :) . csum feature is introduced in libdrizzle last december I think. So not much blogs on it .
Stewart sir: If transaction.proto covers all possible DDL and DML changes then we won't change it. On Mon, Apr 22, 2013 at 11:26 AM, Andrew Hutchings <and...@linuxjedi.co.uk>wrote: > On 22/04/13 01:28, Stewart Smith wrote: > >> kuldeep porwal <2591kuld...@gmail.com> writes: >> >>> If in future if we find some DDL inconsistency or any other issue that >>> *may* require changing transaction.proto then we should modify it and >>> keep >>> that under different version. As this will obviously help in entirely >>> independent working of our module and we don't affect Drizzle slave or >>> applier at the same time. >>> >> >> We should not need to modify transaction.proto at all as it can already >> be used to express all DDL and DML changes possible to apply to Drizzle. >> >> I wouldn't worry too much about it at this stage, we could attempt the >>>> SQL >>>> >>> and just error out if it doesn't apply. >>> Yeah great! I introduced Checksum and DDL heuristics just as a part of >>> proposal. We have to create basic prototype first then we will keep on >>> improving it. >>> >> >> There shouldn't be any place to add in checksum, we can >> support/notsupport the MySQL binlog checksum for reading. >> > > And Libdrizzle 5.1 already supports that in its binlog API :) > > Kind Regards > -- > Andrew Hutchings - LinuxJedi - http://www.linuxjedi.co.uk/ > -- Regards, Kuldeep Porwal IIIT Hyderabad 09550605256 http://web.iiit.ac.in/~kuldeep.porwal
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : drizzle-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
