Re: MDB - Delete LOB

Hello, On 06/09/2003 04:27 AM, 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.

Well but I think if MDB/Metabase creates this data then it should be possible to remove it through MDB/Metabase. Since we can't sensibly do it automatically I think it should be at least be possible to do it manually.

Yes, with PostgreSQL specific function, but not in MDB/Metabase. There is no need to bloat MDB/Metabase API further.

Of course this adds a meaningless method for the rest of the drivers. In order to not pollute Common.php with methods like that I might go the route of just adding it to postgresql and users will then have to check for the methods existence if they want to use this functionality yet use the same code on a different DB. Obviously this is ugly, but I think this is better than not having the functionality in MDB/Metabase. Atleast with MDB I also want to be a nice OO API to a specific database. That is why I am also considering adding autoincrement functionality. In return I am planning to remove a lot of redundant methods in MDB, so overall the MDB API should get leaner.

I don't agree. If you do not see now how much more bloated it will make MDB, you will see it later. If you want to provide functions to support database specific features that are not portable, people will prefer to use the native API because it is not bloated with all the code that they do not need. Bloating the API compromises the scalability of the applications because of all unnecessary the code that needs to be compiled and loaded at run time. -- Regards, Manuel Lemos Free ready to use OOP components written in PHP http://www.phpclasses.org/