Project:
| View Revisions: Issue #35493 | [ Back to Issue ] | ||
| Summary | 0035493: missing log info when check consistency fails | ||
| Revision | 2017-03-13 12:09 by alostale | ||
| Description | When exporting database, PL code is checked to ensure it is consistently exported. When there are inconsistencies it only logs some basic info, but it misses the actual problems. The problem is caused because export.database uses OBLogAppender to log information. This class stores the information about where to log in ThreadLocals, now check consistency is performed in different threads, so the logs generated from these other threads are not displayed. |
||
| Revision | 2017-03-13 12:06 by alostale | ||
| Description | When exporting database, PL code is checked to ensure it is consistently exported. When there are inconsistencies it only logs some basic info, but it misses the actual problems. | ||
| Revision | 2017-03-13 10:00 by alostale | ||
| Steps To Reproduce | 1. Set core in development 2. Do modifications to some PL to force to be inconsistently exported: * ie. change IF TG_OP = 'DELETE' THEN RETURN OLD; ELSE RETURN NEW; END IF; to lower case IF tg_op = 'DELETE' THEN RETURN OLD; ELSE RETURN NEW; END IF; 3. Export database Check the log doesn't indicate the differences you'd get. |
||
| Revision | 2017-03-13 09:59 by alostale | ||
| Steps To Reproduce | 1. Set core in development 2. Do modifications to some PL to force to be inconsistently exported: * ie. change IF TG_OP = 'DELETE' THEN RETURN OLD; ELSE RETURN NEW; END IF; to lower case -> IF tg_op = 'DELETE' THEN RETURN OLD; ELSE RETURN NEW; END IF; 3. Export database Check the log doesn't indicate the differences you'd get. |
||
| Revision | 2017-03-13 09:17 by alostale | ||
| Steps To Reproduce | 1. Set core in development 2. Do modifications to some PL to force to be inconsistently exported 3. Export database Check the log doesn't indicate the differences you'd get. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |