———————————————————————————————————
以前论坛里的：
1、MIDAS/ADO/SQLSERVER中使用BLOB字段时，如果BLOB字段存入的数据太大时，在客户端保存时，系统报保存失败，并且在查询这个有BLOB表数据量太大时，中间层死机。先谢了
2、用BDE开发，在BLOB SIZE型字段里有限制，range:>32,<1000byte。即：当blob字段中内容大于1M时会报错
国外网站的：
SQL LINKS >=4.0 BLOB SIZE parameter
What is the BDE BLOB SIZE parameter used for?
[*Please note that the behavior described below applies only to BDE/SQL Links >=4.0. The Version 4.0 BLOB SIZE param applies to viewing "dead" results as well as live results containing text/blob data if BLOB SIZE is set higher than 32k]
Increasing the BLOB SIZE from the default of 32 will currently prevent opening "dead" (unindexed or Request Live = false) results from returning text data when opening. In other words if BLOB SIZE is increased from 32 then only TQueries that are opened as live results will return data.
From SQL Links 4.0 Help:
BLOB SIZE Determines the fetch buffer size for dead BLOBs. Applications that deal with dead BLOBs using dead table opens or queries or batchmoves can set a maximum limit on the size of BLOBs to fetch. Setting this parameter to 64 means your application can fetch BLOBs of up to 64K. This parameter does not apply to live table opens.
Default Value: 32 Range : >32 and < 000
* Interbase BLOBs are always "live" and are therefore not affected by the BLOB SIZE param
* DB/2 Binding a large buffer for fetching dead blobs by setting the BLOB SIZE setting to max (65535) DB2 returns SQL error "SQL0973N Not enough storage is available in the QUERY_HEAP to process the statement. SQLSTATE=570 " Note: This is a vendor restriction. Increasing the QUERY_HEAP on the server should solve the problem.
3/26/99
1 个解决方案
#1
你使用事务提交呢
#1
你使用事务提交呢