[#517] - Fix broken module installation in Postgresql because of NULL constraint
- Closed
- 4 Mar 2014
- Medium
- Build: master
- # 517
- Diff
- vietvh:pginstaller
- Error default This pull request is targeted at the master branch. Pull requests should no longer be merged to master. Details
User tests: Successful: Unsuccessful:
In Postgresql, if we have a column (TEXT NOT NULL) and we do not specify the column in INSERT, Postgresql will assume that column's value is NULL while MySQL will take it as empty string ''
Yes, adding default value is fine however I checked the DDL of MySQL, PostgreSql and SqlAzure, they do not have default value for those fields, adding default value should be done for those 3 and I just do not have SqlAzure at hand to test so I went with the PHP fix, just faster for me.
Thanks for coding this, Viet Hoang Vu!
While we’re transitioning to a new integrated tracker, could you report the issue on our current main tracker at JoomlaCode and cross-reference each with a link to the other?
Alternatively, let me know if you’d like me to create it for you and I can go ahead and do that.
Thanks in advance and thanks again for coding this, Viet Hoang Vu!
I went ahead and submitted the tracker item:
http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=30838
Thanks again, Viet Hoang Vu!
Closing as this was fixed some time ago
Have you tried to add "DEFAULT '' " to column definition, without this change ?
In this case it's maintained consistency with MySQL, the result is the same without doing whenever code change like this.