弈秋anddev 8a11c99410 fix(dameng): normalise dexp/dimp PARFILE paths and surface the real failure (#12872) ...

dexp/dimp read PARFILE values verbatim, and their documentation lists `"` and `\`
among the characters a FILE/LOG name may not contain. DBX emitted both quoted paths
and Windows back-slash paths, so on Windows the tool rejected the parameters before
opening its LOG file. The caller then read an empty log, `parse_dump_log` fell back
to its generic sentence, and the user saw "dexp/dimp did not report success" with no
parameter, path or exit status named.

- render FILE/LOG as forward-slash paths, quoting only when a space makes the value
  ambiguous (closes #12837)
- carry the child's exit status into the failure message and append the tool's own
  output tail, so the cause is visible even without a log file
- reject whitespace in the USERID fields as well: a space ends the token early, the
  same way `/` and `@` do

Co-authored-by: dev <dev@local>

2026-10-20 20:25:09 +08:00

..

src

fix(dameng): normalise dexp/dimp PARFILE paths and surface the real failure (#12872)

2026-10-20 20:25:09 +08:00

Cargo.toml

refactor(workspace): split SQL and database driver crates

2026-09-25 15:51:58 +08:00