Hello All,
We ran into few issues when running Drupal 4.6.6 with PostgreSQL. The issue, in general, seems to be with some queries in some of the modules that attempted to insert a blank string ('') into an integer field.
The modules affected are: user.module and node.module from Drupal Core, and flexinode module.
I found that this issue has been discussed already at http://drupal.org/node/27870.
I have a patch that fixes this issue reasonably. Please let me know how I should go about contributing it. Perhaps I could post the patch somewhere - either on this list or on one of the forums on drupal.org - and then one of the contributors can propagate it to the source code.
Also, what is best place to post a patch for the fix in flexinode module?
Thanks, Nimish
I have a patch that fixes this issue reasonably. Please let me know how I should go about contributing it. Perhaps I could post the patch somewhere - either on this list or on one of the forums on drupal.org - and then one of the contributors can propagate it to the source code.
Also, what is best place to post a patch for the fix in flexinode module?
Nimish,
The best place to post your patch is the issues pages of the relevant module or if it involves core, the issues pages of the Drupal project:
http://drupal.org/project/drupal http://drupal.org/project/flexinode
On the main project pages you can click on "Report new bug" to submit an issue and the patch if you have any. You can do the same from the issues page (i.e. the page you will be directed after clicking "View pending patches", or "View all issues").
Check also this: http://drupal.org/patch
Good luck.
iZzeT
--------------------------------------------------------------------------
Hello All,
We ran into few issues when running Drupal 4.6.6 with PostgreSQL. The issue, in general, seems to be with some queries in some of the modules that attempted to insert a blank string ('') into an integer field.
The modules affected are: user.module and node.module from Drupal Core, and flexinode module.
I found that this issue has been discussed already at http://drupal.org/node/27870.
I have a patch that fixes this issue reasonably. Please let me know how I should go about contributing it. Perhaps I could post the patch somewhere - either on this list or on one of the forums on drupal.org - and then one of the contributors can propagate it to the source code.
Also, what is best place to post a patch for the fix in flexinode module?
Thanks, Nimish -- [ Drupal support list | http://lists.drupal.org/ ]