| Summary |
0005893: DbCompare should write to standard error and not continue with an invalid date-time format |
|
| Revision |
2023-07-17 18:13 by cquamme |
|
| Description |
When using DbCompare via the command line, currently we will throw an exception in the log. We should write to standard error if the date-time format is incorrect, and not allow DbCompare to continue. |
|
| Revision |
2023-07-17 17:28 by cquamme |
|
| Description |
When using DbCompare via the command line, currently we will throw an exception in the log. We should also write to standard error if the date-time format is incorrect, and not allow DbCompare to continue. |
|
| Revision |
2023-07-17 15:58 by cquamme |
|
| Description |
When using DbCompare via the command line, currently we will throw an exception in the log. We should also write to standard error with the exception message. |
|
| Revision |
2023-07-17 14:35 by cquamme |
|
| Description |
When using DbCompare via the command line, currently we will throw an exception in the log. Instead, we should write to standard error with the exception message, rather than having the entire stacktrace in the log. |
|
| Revision |
2023-06-22 18:21 by cquamme |
|
| Description |
When using DbCompare via the command line, currently we will throw an exception in the log when the date time format is invalid. Instead, we should write to standard error with the exception message, rather than having the entire stacktrace in the log. |