details: https://code.openbravo.com/erp/devel/pi/rev/fbfe1fab2cff changeset: 18181:fbfe1fab2cff user: Augusto Mauch <augusto.mauch <at> openbravo.com> date: Wed Oct 10 09:47:15 2012 +0200 summary: Fixes issue 21817: SQL comments are applied to the proper columns
There was a problem in postgreSQL that happened when a table was created and one of its columns was removed and created again. The ordinal position of the columns in that case is not consecute, i.e. Before removing the column: Ordinal position Name 1 Column1 2 Column2 3 Column3 After removing the column Column2 Ordinal position Name 1 Column1 3 Column3 After adding the column Column2 again Ordinal position Name 1 Column1 3 Column3 4 Column2 When the comments are applied to the columns, instead of using the ordinal position, the index (1..number of columns) was used to determine which comment belongs to each column. This resulted that the comments were applied to the wrong columns. If instead of using the index the ordinal position is used, the problem is solved. diffstat: src-db/database/lib/dbsourcemanager.jar | 0 1 files changed, 0 insertions(+), 0 deletions(-) diffs (2 lines): diff -r dd07b90a28d2 -r fbfe1fab2cff src-db/database/lib/dbsourcemanager.jar Binary file src-db/database/lib/dbsourcemanager.jar has changed ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Openbravo-commits mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openbravo-commits
