Subject | RE: [Firebird-Architect] Firebird Features and SMP |
---|---|
Author | Steve Summers |
Post date | 2006-12-04T13:24:31Z |
-----Original Message-----
From: Firebird-Architect@yahoogroups.com [mailto:Firebird-Architect@yahoogroups.com] On Behalf Of Jim Starkey
Sent: Monday, December 04, 2006 07:39 AM
To: Firebird-Architect@yahoogroups.com
Subject: [Firebird-Architect] Firebird Features and SMP
rare to have ad-hoc queries that are all standard enough to be preparable anyway. OTOH, the Vulcan merge will result in a
higher performance, more easily extensible product. I'd much rather see that happen faster than to get slightly useful features
sooner.
From: Firebird-Architect@yahoogroups.com [mailto:Firebird-Architect@yahoogroups.com] On Behalf Of Jim Starkey
Sent: Monday, December 04, 2006 07:39 AM
To: Firebird-Architect@yahoogroups.com
Subject: [Firebird-Architect] Firebird Features and SMP
>Rather than loading Firebird 2.x with dozens of individuallyEXCELLENT point. While the "In List" feature could be slightly useful, composing queries on the fly is an easy workaround. It's
>insignificant features (IN LIST, for example), would it not make more
>sense to get the Vulcan based code base to product status and out the door?
rare to have ad-hoc queries that are all standard enough to be preparable anyway. OTOH, the Vulcan merge will result in a
higher performance, more easily extensible product. I'd much rather see that happen faster than to get slightly useful features
sooner.