Re: [PHP-DB] Postgres and gzcompress

2006-09-07 Thread John DeSoi
If your goal was to compress the data, this seems counterproductive since base64 will inflate it by 33% or more. I would recommend using a bytea column and a prepared statement to insert or update. This will be faster and you won't have to worry about escaping. On Sep 6, 2006, at 11:18 P

RE: [PHP-DB] Postgres and gzcompress

2006-09-06 Thread Nathan Harmon
= base64_decode(gzuncompress($row[0])); - Nate Original Message Follows From: "Bastien Koert" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], php-db@lists.php.net Subject: RE: [PHP-DB] Postgres and gzcompress Date: Wed, 06 Sep 2006 19:50:42 -0400 Try base_64_encod(ing) it then compre

RE: [PHP-DB] Postgres and gzcompress

2006-09-06 Thread Bastien Koert
Try base_64_encod(ing) it then compressing it. on the way out, uncompress, base-64-decode the value and see what you get Bastien From: "Nathan Harmon" <[EMAIL PROTECTED]> To: php-db@lists.php.net Subject: [PHP-DB] Postgres and gzcompress Date: Wed, 06 Sep 2006 15:39:37 -0700 Hi, I would lik