Hello,
I'm using a Firebird 3 x86 Windows snapshot (SuperServer) from October
15, 2015 using Pavel's OLTP emulator to put load on Firebird, the trace
functionality and our FB TraceManager.
I'm using the following trace configuration:
database = oltpemul.fdb
{
enabled = true
log_statement
Yes, the number of times I have caught out by that little oddity.
On 16/10/15 14:29, Alex Peshkoff wrote:
> Which must be present in the end of struct or class
The underlying point is that an sql script parser doesn't have to do a
complete analysis but does have to break up the text into blocks o
On 10/16/2015 04:22 PM, Tony Whyman wrote:
> Except that there is no more reason for a separator after the final PSQL
> END statement than there is in 'C' for a semi-colon after a closing brace.
Which must be present in the end of struct or class :)
--
Except that there is no more reason for a separator after the final PSQL
END statement than there is in 'C' for a semi-colon after a closing brace.
On 16/10/15 14:01, Ivan Přenosil wrote:
> There are actually two separators/terminators - one to be used in scripts
> to separate commands, one to be
On 16/10/2015 10:07, Dimitry Sibiryakov wrote:
> 16.10.2015 15:01, Ivan Přenosil wrote:
>> There are actually two separators/terminators - one to be used in scripts
>> to separate commands, one to be used inside PSQL commands.
>> The whole problem is caused by the fact that somebody chose
>> the sa
16.10.2015 15:01, Ivan Přenosil wrote:
> There are actually two separators/terminators - one to be used in scripts
> to separate commands, one to be used inside PSQL commands.
> The whole problem is caused by the fact that somebody chose
> the same character for both.
> So the solution by Adriano i
From: Adriano dos Santos Fernandes
> It seems you like to complicate things.
>
> Call "isql -term !" and do not use SET TERM at all, just terminate your
> full commands with "!".
There are actually two separators/terminators - one to be used in scripts
to separate commands, one to be used inside
