Issue Details (XML | Word | Printable)

Key: CORE-3446
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Adriano dos Santos Fernandes
Reporter: Adriano dos Santos Fernandes
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Firebird Core

Allow conversion from/to BLOBs and others types in the API functions (XSQLVAR or blr messages)

Created: 18/Apr/11 09:17 PM   Updated: 27/May/15 03:36 PM
Component/s: API / Client Library, Engine
Affects Version/s: None
Fix Version/s: 2.5.1, 3.0 Alpha 1

Issue Links:
Replace
 

QA Status: Done with caveats
Test Details:
2.5.0:
Statement failed, SQLSTATE = 0A000
Dynamic SQL Error
-SQL error code = -303
-feature is not supported
-BLOB and array data types are not supported for move operation

2.5.1 and 2.5.2: client crash, "INET/inet_error: connect errno = 10061"

2.5.3 and later: works OK, but limit of varchar field is >>> 8187 <<< characters (not 8190)
otherwise get exception:
Statement failed, SQLSTATE = 54000
Dynamic SQL Error
-SQL error code = -204
-Implementation limit exceeded
-block size exceeds implementation restriction

Sent letter to dimitr with all mentioned above, 25-may-2015 13:53


 Description  « Hide
It's allowed to use XSQLVAR (or blr messages) between different types like number->varchar (or vice-versa) but it's not allowed to use different types when one of them is a blob.

DSQL moves data using MOVD_move, which do it like a client move. This was ok before, cause DSQL was not part of the engine and blobs wasn't very integrated with others types. Now it's very inconsistent.

The proposed change makes possible to move blobs to/from different types in the execute and fetch calls.

For input parameters, it is specially good as user can put the parameter as string without need to create and fill a blob from the client side.

For output (execute or fetch), it's good when the application knows it's data and may describe a blob as a string with its maximum length.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.