Hello all, new user of these forums here...
I am using Zend Framework 0.9.2 in a project for my employer. I am connected to a MySQL DB using the Zend Framework and MYSQLI:
Code:
$this->db_dbase = Zend_Db::factory('MYSQLI', $params);
I have found that in a particular table, which has a field of type LONGBLOB, that when there is data in this field, Zend behaves in a strange manner. I am selecting a record from this table in the following manner:
Code:
$sub_table = new subscribers();
$where = array("subscriber_id = '9'");
$values = $sub_table->fetchRow($where);
Depending on which record I select (ie, by changing the record ID pointed to by the where clause), I get different results:
- On one record, the LONGBLOB field is empty, and no errors occur.
- On a different record, there is data in the LONGBLOB field, but depending on how I view/refresh the page containing the above selection code segment (and depending on what page I view before it!), I sometimes get an error (in the Zend Loader class), and sometimes I don't - however, the error is repeatable.
- On yet another record, where there is data in the LONGBLOB field, when I refresh the page things go really haywire - to the point of SEGFAULTing on the server - throwing all sorts of strange errors, in a seemingly random fashion.
I would love to post the data contained in the LONGBLOB fields, but each of the two instances that fail the data is over 1K in length (one is near 2K, the other, 4K) - I don't know if it is the data in the field, or the length of the data, or something else. The field was originally populated with large amounts of $_SESSION variable data - it doesn't seem to be encoded or anything (I would have to dig through some old code to find out exactly how it was stored - from the look of the data, it just looks like a straight dump into the field).
I plan on just eliminating the data from the field, or dropping the field entirely from the table, which should fix the issue for me. I wanted to post this in case anybody else what experiencing similar issues. I am not sure if this issue affects the current version of the Zend Framework (0.9.3) or not, as I have yet to load it into the system and test.
I hope this helps someone out there...