SymmetricDS

Triggers are created without transaction_id function when auto.config.database=false

Details

  • Number of attachments :
    0

Description

When any trigger is created, or recreated, it will put 'null' for transaction_id column in the select that captures de data.

The main consequence I found: If no tx id is captured in data table, Symmetric may create one batch by data because he doesn't know which rows were commited together in the original transaction.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Chris Henson added a comment -

What database platform are you on? Some database platforms don't support transaction ids.

http://symmetricds.codehaus.org/guide/2.4/html-single/user-guide.html#databases

Show
Chris Henson added a comment - What database platform are you on? Some database platforms don't support transaction ids. http://symmetricds.codehaus.org/guide/2.4/html-single/user-guide.html#databases
Hide
Permalink
Juan Rodolfo Ferreyra added a comment -

Sorry, it happened with Postgre 8.4 and 9 on Debian 6.0.1 64 bit servers, with several versions of Symmetric, 2.3.1 in this case. I dropped the bad triggers (and related trigger functions) and restarted Symmetric but they were recreated the same wrong way. When I turned on auto.config.database, they were created correctly.

Show
Juan Rodolfo Ferreyra added a comment - Sorry, it happened with Postgre 8.4 and 9 on Debian 6.0.1 64 bit servers, with several versions of Symmetric, 2.3.1 in this case. I dropped the bad triggers (and related trigger functions) and restarted Symmetric but they were recreated the same wrong way. When I turned on auto.config.database, they were created correctly.

People

  • Assignee:
    Chris Henson
    Reporter:
    Juan Rodolfo Ferreyra
Vote (0)
Watch (0)

Dates

  • Created:
    Updated: