You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by "Henning P. Schmiedehausen" <ma...@hometree.net> on 2001/11/29 17:41:21 UTC
ID Broker - Trouble with multiple DBs
Hi,
we're using multiple Turbine apps with the following database system:
one database, called "TDK" contains all the tables from Turbine.
Basically everything that starts with "TURBINE_" and the ID_TABLE;
multiple databases (one for every application) that contain the
application data tables.
All Turbine Apps are configured like this in TRP:
database.default.driver=org.gjt.mm.mysql.Driver
database.default.url=jdbc:mysql://127.0.0.1/TDK
database.default.username=:-)
database.default.password=:-)
database.DATA.driver=org.gjt.mm.mysql.Driver
database.DATA.url=jdbc:mysql://127.0.0.1/application-data
database.DATA.username=:-)
database.DATA.password=:-)
As you can see, we're using MySQL and the "native" id generation using
autoincrement in the .xml schemes.
This works fine for our stuff, all data is happily separated and yet
all applications use the same set of users.
Now we want to port our application to a database which no longer
supports "native". This means for us that we want to use the id-broker
to create the table ids.
As far as I can see, the id broker does not store the database names
in the ID_TABLE nor does it use different tables for different
databases. We have two applications that both use a table called
"foo". :-) So they will use the same ID_TABLE row to generate the IDs,
wouldn't they?
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
D-91054 Buckenhof Fax.: 09131 / 50654-20
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: ID Broker - Trouble with multiple DBs
Posted by John McNally <jm...@collab.net>.
There should be an ID_TABLE per database.
john mcnally
"Henning P. Schmiedehausen" wrote:
>
> Hi,
>
> we're using multiple Turbine apps with the following database system:
>
> one database, called "TDK" contains all the tables from Turbine.
> Basically everything that starts with "TURBINE_" and the ID_TABLE;
>
> multiple databases (one for every application) that contain the
> application data tables.
>
> All Turbine Apps are configured like this in TRP:
>
> database.default.driver=org.gjt.mm.mysql.Driver
> database.default.url=jdbc:mysql://127.0.0.1/TDK
> database.default.username=:-)
> database.default.password=:-)
>
> database.DATA.driver=org.gjt.mm.mysql.Driver
> database.DATA.url=jdbc:mysql://127.0.0.1/application-data
> database.DATA.username=:-)
> database.DATA.password=:-)
>
> As you can see, we're using MySQL and the "native" id generation using
> autoincrement in the .xml schemes.
>
> This works fine for our stuff, all data is happily separated and yet
> all applications use the same set of users.
>
> Now we want to port our application to a database which no longer
> supports "native". This means for us that we want to use the id-broker
> to create the table ids.
>
> As far as I can see, the id broker does not store the database names
> in the ID_TABLE nor does it use different tables for different
> databases. We have two applications that both use a table called
> "foo". :-) So they will use the same ID_TABLE row to generate the IDs,
> wouldn't they?
>
> Regards
> Henning
>
> --
> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
> INTERMETA - Gesellschaft fuer Mehrwertdienste mbH hps@intermeta.de
>
> Am Schwabachgrund 22 Fon.: 09131 / 50654-0 info@intermeta.de
> D-91054 Buckenhof Fax.: 09131 / 50654-20
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>