Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extend the TracePlugin Interface [CORE3752] #4096

Open
firebird-automations opened this issue Feb 2, 2012 · 2 comments
Open

Extend the TracePlugin Interface [CORE3752] #4096

firebird-automations opened this issue Feb 2, 2012 · 2 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Oleg Matveyev (o_matveev)

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

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

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.

@firebird-automations
Copy link
Collaborator Author

Commented by: Oleg Matveyev (o_matveev)

In the FB3.0 - yes. UTF8 is best choice imho.
But requested function "convertToUTF8" may be short way for now, FB2.5.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant