Re: MDB - Delete LOB
| From: | Manuel Lemos | Date: | Sun, 08 Jun 2003 22:48:20 +0000 |
| Subject: | Re: MDB - Delete LOB | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-17184@lists.php.net to get a copy of this message | ||
Hello,
On 06/08/2003 06:40 PM, Lukas Smith wrote:
Only PostgreSQL behaves like this because it really does not support real BLOBs as they admit in their documentation. To support this limitation of PostgreSQL I do not see much point adding functions that would only be useful when you use it, not to mention all sorts of problems that you need to deal to handle any errors properly. -- Regards, Manuel Lemos Free ready to use OOP components written in PHP http://www.phpclasses.org/Binary strings are not suitable as large objects containers becauseyouhave to paste their whole contents in the query that creates orupdatedthem. This means if it would not exceed your PHP memory limit, itwouldprobably crash your Web server processes when you tried to insertlargedata. MySQL already has this problem. MS-SQL and other databases accessedviaODBC API are in worst situation because the data has to be encoded in hexadecimal (double the size) to be inserted via SQL. PostgreSQL has objects that you can use to store large amounts of data streaming ittothe server. Although PostgreSQL objects are not perfect, I think they are bettertostore large objects than having to deal with the problems of pasting large data in SQL queries.Yeah, but it would probably nice to provide a mechanism to delete these objects within the driver. This sounds like the way to go then.