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

[Chuck Hagenbuch]

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

> 1. Does Horde_Db natively support BLOBs (i.e. it is OK to get rid of  
> use of Horde_SQL::readBlob())

As you seem to have hit with postgres it's inconsistent, but the  
intention is to have it all internally supported. Anything that  
doesn't work, if you write a failing unit test for it, it will be much  
easier to fix and keep fixed (and I will definitely try and look at  
anything with a failing test - easy to motivate and know if you've  
fixed those).

> 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.

Pretty sure that this is missing entirely now. Also, transactions is  
not the same thing as row locking...

-chuck