Fri Feb 20 03:32:46 PST 2009
- Previous message: [Slony1-bugs] [Bug 73] Slony-I: old key column xxx.yyy IS NULL on UPDATE
- Next message: [Slony1-bugs] [Bug 73] Slony-I: old key column xxx.yyy IS NULL on UPDATE
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=73 Adam Buraczewski <aburacze at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aburacze at gmail.com --- Comment #1 from Adam Buraczewski <aburacze at gmail.com> 2009-02-20 03:32:46 --- (In reply to comment #0) > Database statements breaks with the following error: > > Slony-I: old key column product.pictureurl IS NULL on UPDATE > > The columns are NO Key-Columns! I think the source of this problem is the same as in the bug #67 I described in December. Slony-I 2.0.0 introduces a form of "compression" of attkind parameter to _Slony_I_logTrigger() trigger function, but it is not properly handled inside this function. As a result, the trigger randomly treats a non-key column as a key column and expects it to be non-NULL. I prepared a patch and it is attached to the bug #67 (try it, please). The only problem with the patch is that Christopher Browne wanted a sort of regression tests which would clearly show this bug and I couldn't yet deliver such tests (I think it is quite difficult and maybe you have just found a good example). Best regards, Adam Buraczewski -- Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug.
- Previous message: [Slony1-bugs] [Bug 73] Slony-I: old key column xxx.yyy IS NULL on UPDATE
- Next message: [Slony1-bugs] [Bug 73] Slony-I: old key column xxx.yyy IS NULL on UPDATE
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list