On Tue, May 18, 2010 at 3:40 PM, Renat Sabitov <sr...@st...> wrote:
> 18.05.2010 23:29, Cal Heldenbrand пишет:
> > Oh ok, I picked just the status_more_info patch and applied that, I
> > had compilation errors with trying to access a private member in
> > rudiments.
>
> Hm. Neither this patch nor others require private members in rudiments
> (I use 0.32 version). I'll try to apply my patches against the clean
> sqlrelay-0.41 tomorrow and test it for compiling.
>
I can't seem to find the error in my console history... it had to do with
this line:
for (int i=0; i< SEM_COUNT; i++) {
sem[i] = conn->semset->getValue(i);
}
Saying that "semset" is a private data member of that object. I've already
rolled back my source code, but I can try it later after I'm done with the
cursor stuff.
> > Before I go any futher though, has anyone already implemented this?
> > Or do you guys foresee any problems with what I'm trying to do?
> No, I suppose nobody have tried to do this. As for me, in our
> application we use no more than 2 cursors in a moment.
>
Yeah, we usually have at most 5 statements allocated, but it's difficult to
force programmers to close stuff manually in a garbage collected
environment. As a result, we have some pages that go crazy and allocate
hundreds, sometimes thousands of cursor objects. The number of lines of
high level web code is so large, that it's just easier to handle this
management in lower layers.
I'm almost done with the patch, just a few things to clean up and I'll
attach it to an email to the list.
Thanks,
--Cal
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Sqlrelay-discussion mailing list
> Sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlrelay-discussion
>
|
