On Tue, Apr 14, 2009 at 15:37, Mark Phippard <markphip_at_gmail.com> wrote:
> On Tue, Apr 14, 2009 at 9:35 AM, Hyrum K. Wright
> <hyrum_wright_at_mail.utexas.edu> wrote:
>>
>> On Apr 14, 2009, at 7:23 AM, Mark Phippard wrote:
>>
>>> SQLite 3.6.13 was just released. It contains a fix for a problem some
>>> of our users were having using Solaris sparc.
>>>
>>> http://www.sqlite.org/cvstrac/tktview?tn=3777
>>>
>>> So we might want to update our deps tarball to this version for our
>>> next release.
>>
>> Since the bug is something that our users have encountered "in the wild", I
>> think this is reasonable to do. Since we're still several weeks away from
>> 1.6.2, perhaps we should wait and see if there are additional SQLite
>> releases between now and then. During the pre-release housekeeping, we can
>> bump our recommended and shipped versions to whatever is the latest.
>
> FWIW, I did not run into this problem with our CollabNet binaries for
> Solaris sparc. We are using 3.6.10 though. So maybe the problem
> showed up in 3.6.11.
We do not use UNIQUE columns in FSFS, but we do in wc-ng. My initial
read was that the problem was only related to UNIQUE columns (and,
thus, the people having problems are playing with wc-ng), or maybe the
bug is a bit widerspread.
But you certainly won't run into the problem if you've disabled rep-sharing.
Cheers,
-g
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1711655
Received on 2009-04-14 16:51:20 CEST