> -Original Message-
> From: Dmitry Yemanov [mailto:firebi...@yandex.ru]
> Sent: Sábado, 02 de Agosto de 2014 12:15
>
> 01.08.2014 18:55, Simonov Denis wrote:
>
> > SQL> insert into RDB$EXCEPTIONS(RDB$EXCEPTION_NAME) VALUES ('E1');
>
> At the first glance, I don't see why it cannot be p
Dmitry Yemanov wrote Sat, 02 Aug 2014 20:14:38 +0400:
> 01.08.2014 18:55, Simonov Denis wrote:
>
>> SQL> insert into RDB$EXCEPTIONS(RDB$EXCEPTION_NAME) VALUES ('E1');
Note that I did this unprivileged user!
>
> At the first glance, I don't see why it cannot be prohibited. But I see
> from the c
03.08.2014 17:28, Dmitry Yemanov wrote:
> I've just left it to the author to fix.
I don't have commit rights, you know...
> I couldn't run tpcc with this assert activated.
This tpc-c must do something crazy to activate the assert like fetching from
statement
without output parameters or
03.08.2014 18:29, Dimitry Sibiryakov wrote:
>> Commented out the annoying (thus supposedly wrong?) assertion.
>
> Without this assert following code will crash with segfault on using offsets
> array.
> If this assert is activated on queries without output parameters, it should
> be changed
> to
> Commented out the annoying (thus supposedly wrong?) assertion.
Without this assert following code will crash with segfault on using offsets
array.
If this assert is activated on queries without output parameters, it should
be changed
to "fb_assert(count == 0 || offsets)", not just comme
