|Subject||Re: [Firebird-Java] Re: JayBird: Problems with Prepared Statements|
> So you basically mean that it is better, from the standardizationYes, since there is no agreement among JDBC driver vendors on this issue. If
> point of view, to use the driver's vendor-specific extenstions to get
> a String representation for an SQL statement, instead of providing an
> implementation for that with the toString() method?
you use vendor specific extension, you know what you are doing, there are no
conflicts caused by different semantics, etc. If later this issue is covered
in the JDBC specification, we can easily adapt to the change, which will not
be the case if suddenly the specification decides to define some other
meaning for toString() method.
That is my only reasoning, but finally you (I mean the group, all JayBird
users) decide what should be in the driver.