[dev] [commits] Horde branch master updated. 40ca41b9c94a20146cc4a343ac2896e911d81dda

[Michael M Slusarz]

Quoting Michael M Slusarz <slusarz at horde.org>:

> The branch "master" has been updated.
> The following is a summary of the commits.
>
> from: 7536e23b314364bb04c305019545295c211639b7
>
> 27f3db2 SessionHandler rewrite.
> 9c14811 Reset opacity when growler is removed from screen
> 40ca41b Two more places to use Horde_Db_Adapter_Base
>
> -----------------------------------------------------------------------
>
> commit 27f3db208654339614b2fced9677d55729eb37eb
> Author: Michael M Slusarz <slusarz at curecanti.org>
> Date:   Fri May 14 17:30:14 2010 -0600
>
>     SessionHandler rewrite.
>
>     * Abstracted memcache persistent-backend code into 'Stack' driver.
>     * Renamed 'none' driver to 'Builtin'.
>     * Now throws Horde_SessionHandler_Exception.
>     * Split driver code into abstract class.
>     * Use horde/Db to access SQL databases.
>     * Do not rely on Horde::logMessage() (or any of Core).

Some questions arose when converting this code - specifically the DB code:

1. Does Horde_Db natively support BLOBs (i.e. it is OK to get rid of  
use of Horde_SQL::readBlob())
2. Does Horde_Db support row-level locking on Mysql DBs?  With  
Horde_Db, I was able to abstract all of the sessionhandler DB code  
into one driver (instead of separate drivers for Mysql, Postgres,  
Oracle, etc) except for the row-level locking.  Currently, the SQL  
driver is using table level locking (via commit transactions), but I  
am unsure if/how we can do locking at the row level.

michael

-- 
___________________________________
Michael Slusarz [slusarz at horde.org]