Issue Details (XML | Word | Printable)

Key: CORE-3752
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Oleg Matveyev
Votes: 0
Watchers: 3
Operations

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

Extend the TracePlugin Interface

Created: 02/Feb/12 08:42 PM   Updated: 09/Feb/12 05:30 AM
Component/s: API / Client Library
Affects Version/s: 2.5.1
Fix Version/s: None

Environment: Firebird 2.5.1


 Description  « Hide
Currently Trace-log file was writed by using codepage of user connection.
This is potential trouble with using several codepage at a one time.

In the end-user implementation traceplugin we may be use TraceSQLStatement::getTextUTF8(), but has no analog for the statement paramenters.

Improvement request: new method of interface trace-plugin

size_t TraceConnection::convertToUTF8(const char *src, size_t src_size, char *dst, size_t dst_size);

Return Value:
returns the number of char actually converted

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Dmitry Yemanov added a comment - 09/Feb/12 04:18 AM
I would rather suggest that the trace output should be always written in the requested charset (new SPB tag is needed for that purpose) for user trace sessions and in the predefined charset (UTF8? server OS codepage?) for the system audit.

Oleg Matveyev added a comment - 09/Feb/12 05:29 AM - edited
In the FB3.0 - yes. UTF8 is best choice imho.
But requested function "convertToUTF8" may be short way for now, FB2.5.2