View Issue Details

IDProjectCategoryView StatusLast Update
0000421SymmetricDSBugpublic2011-01-02 17:55
ReporterAssigned Tochenson  
Priorityurgent 
Status closedResolutionfixed 
Product Version1.7.14 
Target Version1.7.16Fixed in Version1.7.16 
Summary0000421: The logic for determining support for Postgres transaction identifiers is flawed
DescriptionWe are using SymmetricDS 1.7.14 and we recently upgraded our Postgres DB from 8.4.4 to 9.0.2. After upgrading we saw that the transaction_identifier in the generated DB triggers was coming as null. Earlier this value used to be 'txid_current()'. On checking the source I found the following code segment in class org.jumpmind.symmetric.db.postgresql.PostgreSqlDbDialect: protected void initForSpecificDialect() { if (getMajorVersion() >= 8 && getMinorVersion() >= 3) { . . } I believe this logic is incorrect and fails for major version greater than 8 and minor version less than 3; as we are facing with Postgres 9.0.2.
TagsNo tags attached.

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change