6.0.0-beta1
11/9/25

[#14357] Horde_Share needs support for blob fields.
Summary Horde_Share needs support for blob fields.
Queue Horde Framework Packages
Type Bug
State Resolved
Priority 1. Low
Owners Horde Developers (at) , mrubinsk (at) horde (dot) org
Requester mrubinsk (at) horde (dot) org
Created 05/09/2016 (3471 days ago)
Due
Updated 05/12/2016 (3468 days ago)
Assigned 05/09/2016 (3471 days ago)
Resolved 05/12/2016 (3468 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
05/12/2016 09:03:38 PM Michael Rubinsky Comment #3
State ⇒ Resolved
Reply to this comment
Horde_Share 2.1.0
05/12/2016 09:02:50 PM Git Commit Comment #2 Reply to this comment
Changes have been made in Git (master):

commit ad4b1505f80a88ad64ac7fec0b452226cfec3cce
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date:   Thu May 12 16:59:24 2016 -0400

     Bug: 14357 Fix handling of text/clob fields in the Sql and Sqlng drivers.

     This fixes using shares that contain any 'text' column types
     when using an Oracle backend.

  framework/Share/lib/Horde/Share/Object/Sql.php     |  2 +
  framework/Share/lib/Horde/Share/Sql.php            | 91 
+++++++++++++++++++++-
  framework/Share/lib/Horde/Share/Sqlng.php          |  4 +-
  framework/Share/test/Horde/Share/TestBase.php      |  3 +-
  framework/Share/test/Horde/Share/migration/sql.php |  1 +
  .../Share/test/Horde/Share/migration/sqlng.php     |  1 +
  6 files changed, 98 insertions(+), 4 deletions(-)

http://github.com/horde/horde/commit/ad4b1505f80a88ad64ac7fec0b452226cfec3cce
05/09/2016 01:09:55 AM Michael Rubinsky Comment #1
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Assigned to Horde DevelopersHorde Developers
Assigned to Michael Rubinsky
Queue ⇒ Horde Framework Packages
Summary ⇒ Horde_Share needs support for blob fields.
Type ⇒ Bug
State ⇒ Assigned
Reply to this comment
We need to allow for setting fields that must be represented as blobs 
in the backend. We can't do this in the client code since we (1) have 
no guarantee what backend shares are using and (2) even if we did, we 
don't (and shouldn't) have access to the underlying Horde_Db object in 
client code.

This is needed to prevent errors in RDBMS like Oracle in handling 
'text' fields when we need to allow for arbitrarily large values like 
e.g., in "Description" fields.

Saved Queries