Summary |
0003809: Data extract and routing fallback to contains_big_lob |
|
Revision |
2018-11-29 14:12 by elong |
|
Description |
For dialects like Firebird and Oracle, the data extractor and router service use a substr() technique to quickly extract from sym_data, which can be slow on those platforms due to returning LOB data. The sym_channel.contains_big_lob=1 will select sym_data as LOB, but it's slower, so we default to contains_big_lob=0. Test if the data extracted is cut off, then fall back to behavior of contains_big_lob=1, and warn the user about what happened so they can change the setting if it happens a lot. |
|
Revision |
2018-11-28 18:08 by elong |
|
Description |
For dialects like Firebird and Oracle, the data extractor uses a substr() technique to quickly extract from sym_data, which can be slow on those platforms due to returning LOB data. The sym_channel.contains_big_lob=1 will select sym_data as LOB, but it's slower, so we default to contains_big_lob=0. Test if the data extracted is cut off, then fall back to behavior of contains_big_lob=1, and warn the user about what happened so they can change the setting if it happens a lot. |