Subject | Re: Joins between tables in two different databases? |
---|---|
Author | Svein Erling Tysvær |
Post date | 2006-04-19T07:21:47Z |
--- In firebird-support@yahoogroups.com, "ipai1" wrote:
like a small table, whereas 100 records sounds like an almost empty table.
Firebird is very different from Paradox, and you've hit one of the
differences. There are different ways to cover these differences, I'd
normally have an import routine importing the 30000 records into a
separate table in the other database (normally that could take a few
seconds, but that is hopefully a process that doesn't have to be done
too often). If that for some reason wasn't a good idea, I'd check if
the "joining" could be done in your client program through using
parametres.
HTH,
Set
> G'day all...Hmm, I'd use slightly different wording. To me, 30000 records sounds
>
> I have a requirement for a read-only database (on CD) which has
> tables involved in joins to table(s) held in a read-write database
> somewhere on the hard disk. My existing desktop application uses
> Paradox under the BDE to do this, but I can't seem to find any way
> of doing this with Firebird. Is this possible, and, if so, how would
> I do it? For example, could one create views into a different
> database (a la SQL Server)?
>
> I have a bit of experience with Interbase/Firebird but only in a
> straightforward client/server scenario with a read/write database. I
> would very much like to get away from the Paradox/BDE environment
> and start using embedded Firebird ASAP, so any help would be
> appreciated.
>
> FYI, for this specific application, the read-only table would be
> relatively large (over 30,000 records), but the read-write table
> would be relatively small (around 100 records).
like a small table, whereas 100 records sounds like an almost empty table.
Firebird is very different from Paradox, and you've hit one of the
differences. There are different ways to cover these differences, I'd
normally have an import routine importing the 30000 records into a
separate table in the other database (normally that could take a few
seconds, but that is hopefully a process that doesn't have to be done
too often). If that for some reason wasn't a good idea, I'd check if
the "joining" could be done in your client program through using
parametres.
HTH,
Set