Subject | RE: [Firebird-general] What's missing in Firebird |
---|---|
Author | Claudio Valderrama C. |
Post date | 2005-01-14T04:35:35Z |
Paul Beach wrote:
Firebird as almost everyone knows is not capable of doing cross db queries.
What qli (the original client side tool) does is to retrieve records from
one db, then from other when the user does nested GDML loops. The BDE did
the joins itself when it was required to handle heterogeneous joins, that's
almost the same idea.
But FB, the engine or the whole server is not capable of handling joins from
tables in different databases.
don't remember a conclusion or a general agreement.
C.
>Maybe it's only necessary to fund Ivan Prenosil so he publishes his work.
>>> - Full-Text search capabilities (I know, there are third-party
>>> solutions available, but usually people I know are asking for
>>> a built-in solution)
>
> Anybody want to Sponsor this?
>>> - Cross-Database-QueriesSorry, but this look to me like PR ad. :-)
>
> Extend current SQL implementation to support database.tablename
> notation as was used in QLI. Firebird can do it, its just not
> surfaced in SQL. Sponsor?
Firebird as almost everyone knows is not capable of doing cross db queries.
What qli (the original client side tool) does is to retrieve records from
one db, then from other when the user does nested GDML loops. The BDE did
the joins itself when it was required to handle heterogeneous joins, that's
almost the same idea.
But FB, the engine or the whole server is not capable of handling joins from
tables in different databases.
>>> - Monitoring and Profiling capabilities (to see what's goingIt seems the discussion about Nickolay's tracing API stalled time ago. I
>>> on in the database; running statements, transactions, ...)
>
> Nickolay's Trace API
don't remember a conclusion or a general agreement.
C.