View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005049 | SymmetricDS | Improvement | public | 2021-07-06 18:54 | 2021-07-13 17:53 |
| Reporter | elong | Assigned To | elong | ||
| Priority | normal | ||||
| Status | closed | Resolution | fixed | ||
| Product Version | 3.12.8 | ||||
| Target Version | 3.12.11 | Fixed in Version | 3.12.11 | ||
| Summary | 0005049: Use session_context with JTDS driver | ||||
| Description | The session_context does not currently work with the JTDS driver, only the Microsoft driver. The use of "EXEC" (meant for batch T-SQL) to access the session_context stored procedure is what prevents JTDS from working. Issue 0004847 added a new session_context method to replace context_info as a way to indicate that a batch is being loaded for a source node. The session_context is more reliable because batch scripts and hosted environments like Azure make use of and overwrite context_info. The session_context is easier to understand because it supports named session variables. Issue 0004888 added tests to make sure it can use session_context. However, if someone installed SymmetricDS on SQL-Server prior to 3.12.8, and then upgraded to 3.12.8, 3.12.9, or 3.12.10, they would see source_node_id in sym_data being left empty. | ||||
| Tags | dialect: sql-server | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2021-07-06 18:54 | elong | New Issue | |
| 2021-07-06 18:54 | elong | Status | new => assigned |
| 2021-07-06 18:54 | elong | Assigned To | => elong |
| 2021-07-06 18:54 | elong | Tag Attached: dialect: sql-server | |
| 2021-07-06 18:54 | elong | Project | SymmetricDS Pro => SymmetricDS |
| 2021-07-06 18:56 | elong | Status | assigned => resolved |
| 2021-07-06 18:56 | elong | Resolution | open => fixed |
| 2021-07-06 18:56 | elong | Fixed in Version | => 3.12.11 |
| 2021-07-06 19:00 | admin | Changeset attached | => SymmetricDS 3.12 37965d2a |
| 2021-07-13 17:53 | admin | Status | resolved => closed |