[Bucardo-general] patch for not setting NULL columns in mongo documents

Greg Sabino Mullane greg at endpoint.com
Mon Apr 30 14:17:43 UTC 2012


On Mon, Apr 30, 2012 at 02:55:27PM +0100, Ali Asad Lotia wrote:
...
> The attached patch prevents that error from occurring since it doesn't
> attempt to coerce an unitialized value.

Sounds good to me. Thank you, applied in
b73ef71535c64a8a0afeef91554c1474d82c3d1b.

> If instead people want to insert a NULL value where that column value is null, 
> it may require a configuration setting that allows you to choose between 
> deleting and undefing that object property.

Right. We can worry about that when people start complaining/asking, as you 
are the primary MongoDB user at the moment. :)

-- 
Greg Sabino Mullane greg at endpoint.com
End Point Corporation
PGP Key: 0x14964AC8
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
URL: <https://mail.endcrypt.com/pipermail/bucardo-general/attachments/20120430/2544deda/attachment.sig>


More information about the Bucardo-general mailing list