Subject | Re: [Firebird-Java] Re: JDBC Conformance Document |
---|---|
Author | Blas Rodriguez Somoza |
Post date | 2002-12-13T19:37:45Z |
Hello
At 13/12/2002 18:37 +0000, you wrote:
In fact DatabaseMetaData.getTypeInfo reports since some months ago LONGVARBINARY for BLOB SUB_TYPE 0.
I think the implementation is exactly the same.
Best Regards
Blas Rodriguez Somoza
At 13/12/2002 18:37 +0000, you wrote:
>Could you fix following:I think we agreed BLOB SUB_TYPE 0 is LONGVARBINARY not BINARY.
>
>Section 4. Compliance tests
>
>- remove "Don't exist in FB" for BINARY (as we agreed BLOB SUB_TYPE 0
>is Types.BINARY)
In fact DatabaseMetaData.getTypeInfo reports since some months ago LONGVARBINARY for BLOB SUB_TYPE 0.
I think the implementation is exactly the same.
>- change "Don't exist in FB" to "Not yet supported" for ARRAY. ArraysOK
>are implemented in FB for a long time, but we not have correct Java
>mapping for it.
>Section 6 (end of it)I'll review it again.
>
>"Interclient uses a protocol in which the character values are
>received trimmed, JayBird doesn't." -
>
>Are you 100% sure in this (have you checked)? I remember there was a
>discussion about this issue, and we agreed to keep space padding code
>on the client, because it might happen that server will send a
>trimmed string.
Best Regards
Blas Rodriguez Somoza