X-Original-To: pgsql-php-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 47C8F9FB228 for ; Wed, 2 Aug 2006 15:10:17 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 01760-02 for ; Wed, 2 Aug 2006 18:10:03 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from a2s5.a2hosting.com (host-209-124-50-10.a2webhosting.com [209.124.50.10]) by postgresql.org (Postfix) with ESMTP id C8E309FA4A8 for ; Wed, 2 Aug 2006 15:10:02 -0300 (ADT) Received: from adsl-155-100-31.tys.bellsouth.net ([72.155.100.31] helo=[192.168.1.10]) by a2s5.a2hosting.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.52) id 1G8LAN-00044G-UZ; Wed, 02 Aug 2006 14:10:00 -0400 In-Reply-To: <44D0CD59.8090008@gmail.com> References: <44D0CD59.8090008@gmail.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <436FED1E-67AD-4931-8E27-C81987CF2C49@pgedit.com> Cc: pgsql-php@postgresql.org Content-Transfer-Encoding: 7bit From: John DeSoi Subject: Re: Problem with columns of type Text and Drupal/Prado/PHP5 Date: Wed, 2 Aug 2006 14:09:13 -0400 To: hunkybill@gmail.com X-Mailer: Apple Mail (2.752.2) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - a2s5.a2hosting.com X-AntiAbuse: Original Domain - postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - pgedit.com X-Source: X-Source-Args: X-Source-Dir: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=3.951 tagged_above=0 required=5 tests=FORGED_RCVD_HELO, SPF_HELO_SOFTFAIL, SPF_SOFTFAIL X-Spam-Level: *** X-Archive-Number: 200608/6 X-Sequence-Number: 3577 On Aug 2, 2006, at 12:05 PM, hunkybill@gmail.com wrote: > Examining the database storage for PHP sessions, it uses a column > marked as TEXT to store session data. In my case of integrating not > only Drupal, but Prado, I have extra data from Prado being saved > into the session table. With mysql, columns of type TEXT are > actually BLOBS. When running Drupal and Prado with mysql, session > management works fine. With Drupal, Prado and pgsql however, I have > a serious problem. You need to use the bytea column type. If you need examples, Drupal prior to 4.7 used a text column in their cache table which caused problems with PostgreSQL. In 4.7 it has been changed to bytea. So a comparison of the 4.6/4.7 Drupal sources should give you clues if you want to alter additional fields for binary data because of the Prado. John DeSoi, Ph.D. http://pgedit.com/ Power Tools for PostgreSQL