The Vulcan strategy, not completed, was:
1. Maintain existing API.
2. Move SQL handling into core engine
3. Support JDBC has the interface for the future. New functionality would
be in JDBC first and probably only JDBC.
4. Extend protocol to support native JDBC.
There are efficiencies to be gained with JDBC, particularly with batch
insert. Moving SQL and JDBC into the engine with threads rather than the
BLR looper would be a big performance boost. It would also allow internal
database requests to be structured in SQL rather than GDML, eliminating the
preprocessor dependency.
I don't remember how far I got, but changing startup metadata from hand
coded tables to standard SQL DDL for the core system tables, then layering
other system tables on the core tables to make it easy to extend even the
core system table without a major ODS change.
But the key to all of this is moving SQL into the engine. As much as I
think GDML is a superior DML, SQL won and GDML lost.
On Tuesday, July 29, 2014, Tom Coleman <tcole...@autowares.com> wrote:
>
> On Jul 29, 2014, at 12:35 PM, Carlos H. Cantu wrote:
>
> And what holds them from using Firebird, no matter what decision is made
> about the API?
>
>
> Good question. And what could be holding back everyone else?
>
> See the chart in the reference I posted earlier in this thread.
>
> The line from the movie "Field of Dreams" is especially true in open
> source, "If you build it [well] they [the users] will come."
>
> Point well taken on making problems for existing user base. I'm sure
> Oracle layered JDBC on top of OCI.
>
>
> I'll not discuss what language is better, since such discussions are
> useless and endless. Firebird just need to provide ways for the most used
> languages to access it, and so far, we are doing well in this aspect, since
> we have plenty of drivers for a good number of languages (Java included).
> Delphi still represents a large amount of our user base, so just make sure
> that any changes will not break or cause them any trouble.
>
>
> It's good to have a core user base, but what is the trend?
>
> I just spoke with a company that for a number of reasons would like to
> move some 800 systems off of Delphi.
>
> What language are they considering? Java. Their choice for database
> access? JDBC. Why? Flexibility .
>
> JDBC allows them to code to a widely supported and accepted industry
> standard.
>
> With that port completed they would then have more flexibility to choose
> another database to support their product.
>
> They would then need to be given compelling reasons to stay with Firebird.
>
> There are basically only two options for this project: Grow, or Die.
>
>
>
>
>
--
Jim Starkey
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
