RE: Bug in SQLCl 20.3

Original text of this message