Posted by simmoe on October 23, 2008 at 2:07pm
Jump to:
| Project: | View reference |
| Version: | 6.x-2.8 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
I get - among other things - this:
user warning: BLOB/TEXT column 'field_1_arguments' can't have a default value query: ALTER TABLE content_type_simon_test ADD `field_1_arguments` LONGTEXT DEFAULT '' in C:\Program Files (x86)\drupal-6.5-test\includes\database.mysql-common.inc on line 298.
As soon as i add a new insert view field. The problem is that from here on i can't insert views in my pages - the select list appears but it doesn't store the values when i save the node.
Im a bit puzzled, maye i did something wrong or the module is affected by some other module... any ideas?
Comments
#1
is it 'insert view' or 'view reference'?
#2
#3
#4
Hi - my first post to drupal.org so please excuse if not following protocol..
I had this kind of issue too. I was getting errors like this:
user warning: BLOB/TEXT column 'field_test_arguments' can't have a default value query: ALTER TABLE content_type_menu_item ADD `field_test_arguments` LONGTEXT DEFAULT '' in ... includes\database.mysql-common.inc on line 298.
user warning: Can't DROP 'field_test_arguments'; check that column/key exists query: ALTER TABLE content_type_menu_item DROP field_test_arguments in ... \includes\database.mysql-common.inc on line 322.
user warning: Unknown column 'field_view_ref_arguments'... in ... modules\cck\content.module on line 1213.
I believe it was related to the NULL data type, as detailed on this page:
http://drupal.org/node/386268
So the answer is to change that column using PHPMyAdmin to accept NULL - but Daniel might be able to confirm this.
-----------
Running Apache 2.2.11 Win 32 Vista, PHP Version 5.2.9-2, MySQL 5.1.35, Drupal 6.13, Module 6.x-2.18
#5
yes that's correct, this was fixed in a previous version. I guess the fix was lost, as what tends to happen :/
#6
A new release 2.19 is on it's way. Updating to that and running the upgrade script in drupal should do the trick afaik. If not then you're right about just making that NOT NULL field allow NULL via phpmyadmin. New installations of the module with 2.19+ should work fine.
#7
Thanks v much..