Subject | Re: [ib-support] Cross-db query |
---|---|
Author | Antonio Parrotta |
Post date | 2002-10-30T09:01:27Z |
Svein,
the service dbs use the same table structure, but with different content -
that could be catered for using one table with views that restricted what
was to be visible at any point.
- Everything within the same database (simple, but could be impossible if
off-line access is required)
- Replication (more complicated)
- Export/Import of common data (if your "master" db doesn't have to be 100%
up-to-date all the time)
that" you know you ought to at least consider a different solution ;o{ )
I appreciate and consider so much what people says, but if at this moment I haven't find out a solution, probably I was not so clear. I'm sorry. I explain you the database structure that is working on:
A "Master" db containing the common tables, one or more "Service" db having the same "service" structure, contains 20 tables plus 10 tables that point to the Master db. The application builded from myself, at login time, asks for the name of the service, well, in the windows register, there is an association between the name of the service and the path of Service db. Every time my application has only two connection opened, one to the Master and another one to the Service db. Again, the customer can add as many service db as he want, without asking me for modify the code (or the db structure). He just create an empty Service db(copy, paste and rename and existing db) and the association in the register. Each service can modify any common table and the modification has to be visible to the other service.
Thanks again for your effort, I appreciate so much
Antonio
---------------------------------
MIo Yahoo! : personalizza Yahoo! come piace a te
[Non-text portions of this message have been removed]
>Well, I don't know anything about your "Service" dbs, but my first thoughtwould be to put everything in the same database. My guess is that many of
the service dbs use the same table structure, but with different content -
that could be catered for using one table with views that restricted what
was to be visible at any point.
>Generally I would say that there normally are three possibly good solutionsto problems like yours:
- Everything within the same database (simple, but could be impossible if
off-line access is required)
- Replication (more complicated)
- Export/Import of common data (if your "master" db doesn't have to be 100%
up-to-date all the time)
>I think this list can be a good help in discussing solutions to problemslike yours - and if people like heLen, Ann, Sean or Dmitry says "Don't do
that" you know you ought to at least consider a different solution ;o{ )
I appreciate and consider so much what people says, but if at this moment I haven't find out a solution, probably I was not so clear. I'm sorry. I explain you the database structure that is working on:
A "Master" db containing the common tables, one or more "Service" db having the same "service" structure, contains 20 tables plus 10 tables that point to the Master db. The application builded from myself, at login time, asks for the name of the service, well, in the windows register, there is an association between the name of the service and the path of Service db. Every time my application has only two connection opened, one to the Master and another one to the Service db. Again, the customer can add as many service db as he want, without asking me for modify the code (or the db structure). He just create an empty Service db(copy, paste and rename and existing db) and the association in the register. Each service can modify any common table and the modification has to be visible to the other service.
Thanks again for your effort, I appreciate so much
Antonio
---------------------------------
MIo Yahoo! : personalizza Yahoo! come piace a te
[Non-text portions of this message have been removed]