In FB 3.0 the plan output for stored procs is always PLAN (NATURAL)
whereas with FB 2.5 the plan for each sql statement to be executed
within the SP are returned.
Not having the plan available in FB 3.0 makes it quite difficult to see
what is actually happening in the SP. However, if we take any
25.08.2017 11:38, Paul Reeves wrote:
In FB 3.0 the plan output for stored procs is always PLAN (NATURAL)
whereas with FB 2.5 the plan for each sql statement to be executed
within the SP are returned.
Not having the plan available in FB 3.0 makes it quite difficult to see
what is actually happen
On Fri, 25 Aug 2017 12:28:17 +0300 Dmitry Yemanov wrote
>
> I agree it was handy in simple cases, but it had too many conceptual
> problems.
I accept that for all but the most simple cases the 'plan' was more or
less useless. But just seeing PLAN (NATURAL) is extremely frustrating.
Is there
Hi all,
I'm testing Firebird-3.0.3.32798-0_Win32 client and I found strange
behavior when I canceling event
by isc_cancel_events.
I supposed that after that call, no call back happen, but in reality it
is happen.
Is it correct?
Slavek
--
Ing. Slavomir Skopalik
Executive Head
Elekt Labs s
> I supposed that after that call, no call back happen, but in reality it
> is happen.
>
> Is it correct?
I'd say it is (I have the same in FirebirdClient during tests under
load) and even understandable. Given by design it's 2nd "channel" and
the processing between regular connection and aux co
25.08.2017 13:06, Paul Reeves wrote:
Is there a simple hack I could do to build FB3.0 with the plan enabled
for SPs?
Not so simple, as the code was completely refactored. I will try to
provide you with a patch during the next days.
But whatever happened to the SP debugger?
AFAIK, it was
But I'm talking about fbclient.dll.
It is problematic, because in that concept mean, one times when you give
a call back address.
fbclient can call any time during application run independently to
isc_cancel_event.
I did see any problem with second channel. In normal model when I
canceling
On 25.08.2017 13:36, Slavomir Skopalik wrote:
Hi all,
I'm testing Firebird-3.0.3.32798-0_Win32 client and I found strange
behavior when I canceling event
by isc_cancel_events.
I supposed that after that call, no call back happen, but in reality
it is happen.
Is it correct?
One callba
Not exactly,
procedure EventCallback(P: Pointer; Length: Short; Updated: PByte); cdecl;
var e:TFBEvents;
begin
if (Assigned(P) and Assigned(Updated)) then begin
e:=TFBEvents(p);
try
e.FSO.Enter;
e.EventsReceived := true;
if e.ResultBuffer<>nil then
Move(Updated
On Fri, 25 Aug 2017 14:00:03 +0300 Dmitry Yemanov wrote
>
> > But whatever happened to the SP debugger?
>
> AFAIK, it was never started (although was discussed a bit).
>
And while on the subject of a debugger for SPs...
There are commercial Stored Procedure debuggers available. And I've
oft
On 25/08/2017 11:06, Paul Reeves wrote:
> On Fri, 25 Aug 2017 14:00:03 +0300 Dmitry Yemanov wrote
>
>>> But whatever happened to the SP debugger?
>> AFAIK, it was never started (although was discussed a bit).
>>
> And while on the subject of a debugger for SPs...
>
> There are commercial Stored P
Thank you for the answer
great news :)
regards,
Karol Bieniaszewski
-Oryginalna wiadomość-
From: Dmitry Yemanov
Sent: Friday, August 25, 2017 6:09 AM
To: For discussion among Firebird Developers ; livius
Subject: Re: [Firebird-devel] Firebird 4.0 Alpha 1 release is available for
te
12 matches
Mail list logo
