Could you keep the old method names and signatures?

@kimjand added a method, that differs from existing one (see javadoc), not sure what you @vlsi mean with keeping the old names?

Could you keep the old method names and signatures?

@kimjand added a method, that differs from existing one (see javadoc), not sure what you @vlsi mean with keeping the old names?

Instead of using toStringLiteral() use toString()

Could you keep the old method names and signatures?

@kimjand added a method, that differs from existing one (see javadoc), not sure what you @vlsi mean with keeping the old names?

Instead of using toStringLiteral() use toString()

From javadoc, I'd assume this was on purpose. @kimjand could you comment on this?

Would be great if we can get the fix into next release, as this blocks our update to recent versions.

I'm working on this. Please let me have a couple of days more

Looks like for toString we need the following:

@Nullable ParameterList params; // optional
boolean standardConformingStrings;
boolean idempotent; // == skipInputStreams

I wonder if we use an interface for it instead of (boolean, boolean) parameters?

Currently we have

String toString(@Nullable ParameterList params, boolean standardConformingStrings);
String toExecutable(@Nullable ParameterList params, boolean standardConformingStrings);

What if we go for the following?

interface SqlContext {
  boolean getStandardConformingStrings();
  boolean getIdempotent();
}

@Deprecated
String toString(@Nullable ParameterList params, boolean standardConformingStrings);

String toString(@Nullable ParameterList params, SqlContext context);

I'm happy with the current state of the PR.
Reviews are welcome.
Will merge the PR in a couple of days.

LGTM