Re: DB_Binary Draft

"Stig Sæther Bakken" <ssb@fast.no> wrote in message >speed things up. I don't see why binary data should be treated >different than other data. The prepare/execute methods already have >some BLOB support in the syntax (you can use "&" instead of "?" to >read data from a file). I'm sorry but I didn't really understand this. But for example, post gress handles binary files usilng lo_??? functions, in oracle you'll need some specific code to save the binary file in a LOB, while reading it could be done with a simple sql (with DBMODE_ASSOC). I really don't know how other databases handle this but I'm sure most of them have some spcific way of doing it (excep mysql). Now if you think it should be included in the DB class, it would require at least a setup fields method to configure where the data will be going, a dbsave and dbfetch method and a stream method which will print it to the browser using a propper http header. The point is if this is done all dbtype_? classes have to be updated and can only write this for oci8/pg wouldn't this break compatibility. In short should it be an extra extention or and addition to PEAR::DB --yavo