> I mean ExternalEngine::getCharSet, the function to set connection
> charset for plugin management code.
I see getCharSet on IExternalProcedureImpl only. Nothing on
IExternalEngineImpl. :\
Anyway. I have there strncpy(name, "UTF-8", nameSize);, nothing else...
> If you set charset there, I supp
On 01/08/2017 02:52, Jiří Činčura wrote:
>> This method changes the connection charset whiling the execute/open
>> method is in progress.
> What is this good for?
>
When an attachment runs external code, it may be in three different
"states":
- User (client) code (PSQL / SQL)
- Plugin management
> This method changes the connection charset whiling the execute/open
> method is in progress.
What is this good for?
> It does not change how parameters are described.
>
> I suppose you can use ExternalEngine::getCharSet to change the default
> charset to map parameters.
You mean IMetadataBui
On 27/07/2017 03:01, Jiří Činčura wrote:
> Looks like it has no effect, though it is called. Using WIN1250 there
> and I'm still getting the varchars in UTF-8 (connection charset). So
> it probably has different purpose?
>
>
This method changes the connection charset whiling the execute/open
method
Looks like it has no effect, though it is called. Using WIN1250 there and I'm
still getting the varchars in UTF-8 (connection charset). So it probably has
different purpose?
--
Mgr. Jiří Činčura
https://www.tabsoverspaces.com/
On Mon, Jul 24, 2017, at 11:56, Jiří Činčura wrote:
> Hi *,
>
> do I
Hi *,
do I understand correctly that the IExternalProcedureImpl::getCharSet
allows me to tell engine in what charset I want the varchar/char values?
Because although I have UTF-8 hardcoded there, when I declare procedure
parameter as "result varchar(1) character set ascii" I'm getting
length==1 in
