Title: | DECtrace V2.0 and All-in-1 Perf Rpts conf. |
Notice: | Kits+Doc, 2 | Patches, 3 |
Moderator: | OMYGOD::LAVASH |
Created: | Mon Apr 26 1993 |
Last Modified: | Mon Jun 02 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 467 |
Total number of notes: | 2058 |
I have a customer who is trying to use the BLR to SQL converter, but some of the sql statements generated seem to be hitting some 1024 byte limit. I am assuming that it is hitting this: If a string containing an sql statement is a character literal, then the limit is 1024 bytes. The customer has some statements that are greater than 1024... is there anyway for him to use the converter, but get around this limit so that his large sql statements get converted properly? Thanks, Renee
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
447.1 | Know problem, no feasible fix | OOTOOL::CRAIG | Mon Mar 10 1997 11:23 | 17 | |
Hi Renee, This is a known restriction with a Rdb module. The lowest levels of the I/O module have no context for trapping the error. It would require a redesign/reimplementaion of the module and does not seem feasible to fix in Rdb. There is no workaround for the customer to permit the customer to convert his large statements. The suggested workaround is to manually export the schema with the RMU command and remove any SQL statements which are larger than 1024. Best regards, Sheri |