Description of problem: Postgres plugin is showing not none of the columns are nullable, when in fact some of them are. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Open a table with both nullable and non-nullable columns 2. Go to configuration and view current status 3. Actual results: None of the columns are nullable Expected results: Should show some columns with nullable box checked and some without. Additional info: This might because of a bug in the postgresql-jdbc-driver, it's not necessarily filling "IS_NULLABLE" info correctly.
Fixed in master: commit 7eec179000bb53950f4d6c4eebeef0b33821e79b Author: Michael Burman <miburman> Date: Tue Aug 12 23:09:37 2014 +0300 [BZ 1117830] Parse nullable from NULLABLE instead of IS_NULLABLE
Cherry-picked over to release/jon3.3.x commit 7f014598b83b351063540731ed93a83bb5f86711 Author: Michael Burman <miburman> Date: Tue Aug 12 23:09:37 2014 +0300 [BZ 1117830] Parse nullable from NULLABLE instead of IS_NULLABLE (cherry picked from commit 7eec179000bb53950f4d6c4eebeef0b33821e79b) Signed-off-by: Thomas Segismont <tsegismo>
Moving to ON_QA as available for test with the following brew build: https://brewweb.devel.redhat.com//buildinfo?buildID=381194