apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bojan Smojver <bo...@rexursive.com>
Subject Re: [PATCH]: improved error reporting for apr_dbd_mysql.c - correct version
Date Mon, 22 May 2006 04:34:42 GMT
Quoting Alex Dubov <oakad@yahoo.com>:

> However, with CLIENT_FOUND_ROWS I would prefer the
> "changed rows" behavior, not the "matched rows" one.
> May be additional parameter to connection string will
> do.

OK. MySQL seems to be the odd one out here - Oracle seems to do what  
PostgreSQL/SQLite3 do. Never mind, I'll work on the flags...

> After all, it's not unreasonable to
> have a MEDIUM TEXT/BLOB (24MB) fetched in one chunk on
> modern machine. To conclude - do you have any thoughts
> on how to implement this in apr way?

Maybe we can also use the flags to _open for that? In other words, we  
can say in the connect string:

flags = CLIENT_FOUND_ROWS,MAX_FIELD_SIZE_24MB

Then we parse those things (as strings, of course) and convert them to  
relevant flags, options and what not. Manual, but safe.

> Mysql likes to crash if parameter/result arrays are
> not zeroed fully before bind calls. I'm using pcalloc
> for everything because of that.

Right. I noticed that in the patch.

-- 
Bojan

Mime
View raw message