View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003388 | SymmetricDS | Bug | public | 2018-01-21 21:18 | 2019-08-26 12:45 |
Reporter | snpe | Assigned To | elong | ||
Priority | normal | ||||
Status | closed | Resolution | open | ||
Product Version | 3.9.2 | ||||
Summary | 0003388: SQL Anywhere triggers issue | ||||
Description | SymmetricDS creates T-SQL triggers on SQLAnywhere - http://dcx.sybase.com/1200/en/dbreference/create-trigger-tsql-statement.html These triggers have default ORDER 1 and always run BEFORE other database "after" triggers (other triggers have to have ORDER > 1 when using Symmetricds). So, the changes created by other database triggers aren't replicated. Solution: convert SQLAnywhere triggers to WATCOM SQL - http://dcx.sybase.com/1200/en/dbreference/create-trigger-statement.html | ||||
Steps To Reproduce | - create a trigger in SQLAnywhere that change something. The changes within triggers will not be replicated. | ||||
Additional Information | I'm willing to update a patch since I have fixed it for us, but we have to use patched SymmetricDS on SQL Anywhere 11. | ||||
Tags | dialect: sql anywhere | ||||
|
If you sign the online CLA and submit a patch, we'll merge it in: https://www.symmetricds.org/developer/contributor |
|
Auto closing all issues waiting for feedback after 4 months. We don't have enough information to take any action. |
Date Modified | Username | Field | Change |
---|---|---|---|
2018-01-21 21:18 | snpe | New Issue | |
2019-04-24 17:19 | elong | Tag Attached: dialect: sql anywhere | |
2019-04-24 17:23 | elong | Assigned To | => elong |
2019-04-24 17:23 | elong | Status | new => feedback |
2019-04-24 17:23 | elong | Note Added: 0001432 | |
2019-08-26 12:45 | admin | Note Added: 0001582 | |
2019-08-26 12:45 | admin | Status | feedback => closed |