23.07.2016 08:44, Geoff Worboys wrote:
> Ergo: the character set of the parameters to an EXECUTE BLOCK
> come from the attachment character set and NOT from the
> declared character set.
>
> You say "of course, parameters are converted to client charset"
> but this is both far from obvious and con
EXECUTE BLOCK parameter character set comes from attachment not declaration
---
Key: CORE-5316
URL: http://tracker.firebirdsql.org/browse/CORE-5316
Project: Firebird Core
Adriano dos Santos Fernandes wrote:
> On 22/07/2016 08:38, Geoff Worboys wrote:
>> the other regarding EXECUTE BLOCK parameters:
> You did not put full test case here, so I do not know what
> you mean.
> Of course, parameters are converted to client charset, even
> if they use explicit character
On 22/07/2016 10:04, Roman Simakov wrote:
> 2016-07-22 15:54 GMT+03:00 Adriano dos Santos Fernandes :
>> So any change here will cause a problem with old tools, right?
> I'm asking some explanations but do not suggest to fix it right now.
> IMO it's ugly a little bit but why? Just legacy mistake? M
Hello, All.
When a provider receive, for example, ITransaction* as a parameter for a
method, can it
be sure that this is the object it returned from startTransaction() before?
For example, can Y-valve get JTransaction from engine, but use YTransaction
to call
createBlob()?
--
WBR
2016-07-22 15:54 GMT+03:00 Adriano dos Santos Fernandes :
> So any change here will cause a problem with old tools, right?
I'm asking some explanations but do not suggest to fix it right now.
IMO it's ugly a little bit but why? Just legacy mistake? Maybe not,
maybe someone can explain it. Maybe it
On 22/07/2016 09:43, Roman Simakov wrote:
> 2016-07-22 15:17 GMT+03:00 Adriano dos Santos Fernandes :
>> Is there any problem with isql extraction?
>>
>> Does it also manually adds AS for one and not for the other?
>
> No problem but two the same places with different processing. IMO it's
> strang
2016-07-22 15:17 GMT+03:00 Adriano dos Santos Fernandes :
> Is there any problem with isql extraction?
>
> Does it also manually adds AS for one and not for the other?
No problem but two the same places with different processing. IMO it's strange.
--
С уважением
Роман Симаков
Директор департаме
Adriano dos Santos Fernandes wrote:
> On 22/07/2016 08:38, Geoff Worboys wrote:
>> the other regarding EXECUTE BLOCK parameters:
> You did not put full test case here, so I do not know what
> you mean.
> Of course, parameters are converted to client charset, even
> if they use explicit character
On 22/07/2016 08:38, Geoff Worboys wrote:
> the other regarding EXECUTE BLOCK parameters:
You did not put full test case here, so I do not know what you mean.
Of course, parameters are converted to client charset, even if they use
explicit character sets.
Adriano
-
On 22/07/2016 08:37, Roman Simakov wrote:
>
> It's not uniform, consistent. Is there some explanation?
>
>
Is there any problem with isql extraction?
Does it also manually adds AS for one and not for the other?
Adriano
---
UDF by descriptor parameters sometimes get ttype_dynamic for character set
--
Key: CORE-5315
URL: http://tracker.firebirdsql.org/browse/CORE-5315
Project: Firebird Core
Adriano dos Santos Fernandes wrote:
> On 22/07/2016 02:49, Geoff Worboys wrote:
>>
>> Is this expected behaviour?
> No, I think. ttype_dynamic should not escape from the engine.
Okay, I'll raise a tracker item for it.
...
I'm wondering if there might be two issues items going on here.
One regar
Hello!
I've noticed in parser thet for triggers source include "AS" but for
functions and procedures not!
psql_procedure_clause
: procedure_clause_start AS local_declaration_list full_proc_block
{
$$ = $1;
$$->source = makeParseStr(YYPOSNARG(3), YYPOSNARG(4));
$$->localDeclList = $3;
$$->body = $
On 22/07/2016 02:49, Geoff Worboys wrote:
>
> Is this expected behaviour?
No, I think. ttype_dynamic should not escape from the engine.
Adriano
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and tr
15 matches
Mail list logo
