Hey guys,
We're valgrinding drizzle at the moment and see a lot of:
#
==3378== 40 bytes in 1 blocks are still reachable in loss record 14 of 121
#
==3378==at 0x4A06D5C: operator new(unsigned long)
(vg_replace_malloc.c:230)
#
==3378==by 0x5894A8:
drizzled::message::protobuf_BuildDesc_tabl
I am trying out what changes he suggested uptil now I am able to
compile but gtests are failing. I will update discussion once I am
able to find out whats going with gtests.
Vikram
On Jun 22, 4:34 pm, Kenton Varda wrote:
> I haven't heard from the patch author since my previous mail. :/
>
> On
I haven't heard from the patch author since my previous mail. :/
On Mon, Jun 22, 2009 at 4:06 PM, vikram wrote:
>
> Can somebody point out when this patch will be included in source?
> I am trying to do compilation on Solaris 10 but right now I am getting
> errors as mentioned in this post.
>
>
Can somebody point out when this patch will be included in source?
I am trying to do compilation on Solaris 10 but right now I am getting
errors as mentioned in this post.
Vikram
On Jun 4, 1:42 pm, Kenton Varda wrote:
> Thanks for the patch!
> It looks like you were using the examples as a tes
Sorry, Protocol Buffers do not provide support for searching or indexing.
All protobuf does is parse and serialize data structures. Drizzle is
actually building database functionality *on top* of protocol buffers --
they implement their own searching and indexing, using protocol buffers to
implem
Hi Green,
AFAICT, protocol buffers does not have inbuilt support for searching
and querying, at least not in the public domain release.
However, you should be able to use protocol buffers in your particular
scenario. Since your data is more or less read-only once it's
serialized, you should be ab
