Subject | Re: [Firebird-Architect] GPRE |
---|---|
Author | Jim Starkey |
Post date | 2010-02-09T14:48:14Z |
Alexander Peshkoff wrote:
SQL into the engine where it belongs.
It's time to rethink old ideas and adopt to at least the 1990s. SQL
won, BLR lost, get over it.
while I was learning C and Xenix. It predates the engine by about a month.
to compilation time. It doesn't matter any more.
--
Jim Starkey
NimbusDB, Inc.
978 526-1376
[Non-text portions of this message have been removed]
> On Tuesday 09 February 2010 05:40:02 Peter Faulks wrote:Why? It's obsolete. And it's a crutch that lets Firebird from pushing
>
>> Is blr here to stay?
>>
>
> yes
>
SQL into the engine where it belongs.
It's time to rethink old ideas and adopt to at least the 1990s. SQL
won, BLR lost, get over it.
>Not one of the oldest -- the oldest. It was the first thing I wrote
> gpre is very old program. If I'm not mistaken, it's one of oldest firebird
> components. Currently our project supports it mainly for internal use - gpre
> is needed to build firebird, because parts of engine and utilities are
> written using GDML.
>
while I was learning C and Xenix. It predates the engine by about a month.
> If you wish to spend some time enhancing gpre (or writing new embeddedThe idea of BLR was to move the cost of language processing from runtime
> preprocessor) - very good, and welcome to firebird developers list
> (firebird-devel@...)! What about ways to make embedded SQL
> be in sync with dynamic one - suppose the best way is to use same parser /
> blr generator in both cases.
>
to compilation time. It doesn't matter any more.
--
Jim Starkey
NimbusDB, Inc.
978 526-1376
[Non-text portions of this message have been removed]