When I enabled it it showed me this error:
user warning: BLOB/TEXT column 'default_component' can't have a default value query: CREATE TABLE project_issue_projects ( `nid` INT unsigned NOT NULL DEFAULT 0, `issues` TINYINT NOT NULL DEFAULT 0, `components` TEXT DEFAULT NULL, `default_component` TEXT NOT NULL DEFAULT '', `help` TEXT DEFAULT NULL, `mail_digest` VARCHAR(255) NOT NULL DEFAULT '', `mail_copy` VARCHAR(255) NOT NULL DEFAULT '', `mail_copy_filter` VARCHAR(255) NOT NULL DEFAULT '', `mail_copy_filter_state` VARCHAR(255) NOT NULL DEFAULT '', `mail_reminder` TINYINT NOT NULL DEFAULT 0, PRIMARY KEY (nid) ) /*!40100 DEFAULT CHARACTER SET UTF8 */ in /path/to/drupal/includes/database.inc on line 515.
user warning: Table 'd6.project_issue_projects' doesn't exist query: SELECT n.nid, pip.nid AS pip_nid FROM node n LEFT JOIN project_issue_projects pip ON n.nid = pip.nid WHERE n.type = 'project_project' AND pip.nid IS NULL in /path/to/drupal/sites/default/modules/project_issue/project_issue.install on line 411.
user warning: Table 'd6.project_issue_projects' doesn't exist query: SELECT n.nid, pip.nid AS pip_nid FROM node n LEFT JOIN project_issue_projects pip ON n.nid = pip.nid WHERE n.type = 'project_project' AND pip.nid IS NULL in /path/to/drupal/sites/default/modules/project_issue/project_issue.install on line 411.
I fixed it by taking off the line for default in default_component field.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 456468-3.default_component_varchar.patch | 1.16 KB | dww |
Comments
Comment #1
dwwpgsql or mysql?
Comment #2
jfha73 commentedmysql
Comment #3
dwwDuly noted. Wonder why I didn't see that error, then. Maybe it's a MYSQL_STRICT thing. Anyway, please try this and let me know if it solves it for you.
Comment #4
jfha73 commentedAs I said before, I took off that line and it worked, but I'm glad I helped to make it better.
Comment #5
dwwjfha73: Yes, I saw your comment that removing the 'default' definition works if you. That's not what my patch in #3 does. Can you please test it (on a clean test site installation) and let me know if it also works? If so, I'd rather do that -- there's no need for a full text field for this, we can use the (cheaper) varchar instead. Thanks!
Comment #6
jfha73 commentedThat would be a problem because I don't have a clean installation at this point, but if I can get one I'll give it a try.
Comment #7
dww@jfha73: Always have a test site. ;) Your life will be much happier (and safer) that way.
Comment #8
jfha73 commentedI know, I'm doing all this on my test site, that's why I don't have another one where to do it so I'm doing it to this one.
Comment #9
jfha73 commentedSo far it's working fine, I do have a problem with the path project (I don't know if that's your concern too) if it is, here is the path to see the error I get:
http://drupal.org/node/457604
Thanks for all your help.
Comment #10
dww@jfha73:
- "Fixed" means a maintainer committed the fix to CVS, not "I don't have this problem any more". ;)
- What do you mean "So far it's working fine"? Did you in fact apply the patch and try to install again? Your comments aren't clear, but they don't imply you've done this. All I'm asking is that you confirm that with the patch installed, given your mysql configuration, you can cleanly install the project_issue module again without SQL errors.
If you only have a single test site, you could test this by doing the following:
0) Put the site off-line (if anyone other than you might be trying to do anything with it)
1) take a mysqldump
2) disable project_issue
3) uninstall project_issue
4) apply the patch
5) install project_issue
6) drop the database
7) revert to your mysqldump
8) Put the test site back online
9) reply to this issue with information about what happened at step #5.
Thanks,
-Derek
Comment #11
jfha73 commentedI applied the patch an disabled->uninstalled and enabled it again, no errors showed up
Comment #12
dwwYay, thanks!
http://drupal.org/cvs?commit=208792
Now it's "fixed". ;)
Cheers,
-Derek