Thanks for suggestion/comment; it was obvious that DBD::InterBase module has limit of exactly 1 MB while fetching data from the database; unfortunately I just can't find where that limit "lies" to change or even remove it! Other thing is that I prefer limit of 10MB instead!

As I said, in my script(s) I use MEMO as well as BLOB field, and in this case data (in the BLOB field) is already zip-ed (so, there I fetch binary data):

#     . . . . . - rest of the code
# here, NAME is CHAR(16) -not so important, while DATA is BLOB field!
$sql = "SELECT NAME, DATA FROM DOCUMENTS WHERE DOCNAME='$something'";
# $something was previously defined!
    $sth = $dbh->prepare($sql) or die "Preparing: ", $dbh->errstr;
    $sth->execute or die "Executing: ", $sth->errstr;

    $ii = 1;
    $name = "";
        # fetching the content
    while (@row = $sth->fetchrow_array()) {
        foreach (@row) {
            if ($ii%2 == 1) {
        # so it is DOKUMENT's NAME!
                $name = $_;
            } else {
        # so, this is DATA!
    # opening FILE HANDLER for writing the content of the BLOB field
                open (F, ">./$name");
                binmode F;
        # saving into the file "$name"!
                print F "$_";
                close F;
                $name = "";
            };
            $ii++;
        };
    };    
    $sth->finish;
    $dbh->commit or warn $dbh->errstr;
    $dbh->disconnect or warn $dbh->errstr;
#     . . . . . - rest of the code
[download]

so, I think that deflating and inflating is not a good idea. The same reason (binary data) is why I don't want to "break a large field into several rows" but prefer to change LIMIT from the default size of 1MB to 10MB.

But, where and how can I fix that?

Regards, Pet.