Fb 3 introduces local sub routines in stored procedures.
It seems these sub routines cannot call themselves nor can then call
previously declared routines, this is, I assume, by design?
README.subroutines.txt:
Limitations:
1) Subroutines may not be nested in another subroutine.
Rename CryptPlugin parameter in config file
---
Key: CORE-4605
URL: http://tracker.firebirdsql.org/browse/CORE-4605
Project: Firebird Core
Issue Type: Improvement
Components: Engine
So, when I'll be able to compile external modules without including half of
FB sources
into it?..
--
WBR, SD.
--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted
On 11/13/14 16:14, Dimitry Sibiryakov wrote:
13.11.2014 14:10, Alex Peshkoff wrote:
First will definitely be rejected.
Reason?
A lot of serious advantages without serious disadvantages.
--
Comprehensive Server
13.11.2014 14:21, Alex Peshkoff wrote:
A lot of serious advantages without serious disadvantages.
A little external adapter between fixed PAC and CLOOP has them even more.
--
WBR, SD.
--
Comprehensive Server
On 11/13/14 16:24, Dimitry Sibiryakov wrote:
13.11.2014 14:21, Alex Peshkoff wrote:
A lot of serious advantages without serious disadvantages.
A little external adapter between fixed PAC and CLOOP has them even more.
What do you mean by PAC here? In http://en.wikipedia.org/wiki/PAC I've
13.11.2014 14:32, Alex Peshkoff wrote:
What do you mean by PAC here?
Pure Abstract Classes.
--
WBR, SD.
--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through
On 11/13/14 16:37, Dimitry Sibiryakov wrote:
13.11.2014 14:32, Alex Peshkoff wrote:
What do you mean by PAC here?
Pure Abstract Classes.
Dmitry, sorry. I have no time for explaining PAC disadvantages once
more. It was already done it in a summer time. Wire compression is
waiting for me.
13.11.2014 14:48, Alex Peshkoff wrote:
I have no time for explaining PAC disadvantages once
more. It was already done it in a summer time.
Unfortunately, I have time to repeat:
A bug in FPC is not a disadvantage. The rest of problems came from
(pointless)
interface autoupgrade. Getting
You has always the option to clone the tree, fix everything in the
best way, as you're wiser than everybody, and submit a patch.
Such patch will be rejected for sure (even if someone look at it at all)
because
it will revert interfaces to plain abstract classes + clean autoupgrade
13.11.2014 15:43, Leyne, Sean wrote:
If you need something that was idled/deprecated years ago, why are you
'blaming' Adriano for the fact that you will need to do work for your fork?
I'm blaming Adriano for the fact that he broke the interface which worked
just a week
ago and did it in a
Improve Windows installer web page loading in the end of installation
-
Key: CORE-4608
URL: http://tracker.firebirdsql.org/browse/CORE-4608
Project: Firebird Core
Issue
with recursive: provide ability to define recursive part as DERIVED table
-
Key: CORE-4609
URL: http://tracker.firebirdsql.org/browse/CORE-4609
Project: Firebird Core
13 matches
Mail list logo
