apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Dubov <oa...@yahoo.com>
Subject Re: [PATCH]: improved error reporting for apr_dbd_mysql.c - correct version
Date Mon, 22 May 2006 05:05:54 GMT
> > flags = CLIENT_FOUND_ROWS,
What the oracle does if BEFORE UPDATE trigger prevents
updating of matched rows? I believe that matched rows
will only differ from "updated" ones in the presence
of suitable trigger.

> MAX_FIELD_SIZE_24MB
I just thought that no such trickery is needed with
linux. Linux (and curiously WinCE, but not Win32) use
speculative allocation, so one can actually malloc 2GB
of space without much problems and with only 1 page of
wasted RAM (given a 64b addresses or proper kernel).
Of course, this is not so portable behaviour. And for
some reason (I just noticed it), apr_palloc is
synonymous to apr_pcalloc and does memset on allocated
region - this is very bad in light of the above. Given
this, can we have a apr_xxalloc function that does not
touches allocated block? This will make a great
improvement in physical memory usage (at least on
linux).



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Mime
View raw message