-
working on this, i'm convinced that all database schema scripts should be located in one(!) place. IMHO, it's less error-prone to move the pubsub schema to tigase-server.
hmm, what actually keeps you from merging both projects into one repository? the current state appears overly complex.
-
PubSub is a separate project from the Tigase. In factwe have a few PubSub implementations working with/on the Tigase. There is no reason in putting all of them into a single repository. On the contrary, I am in favor of splitting bigger beings into a smaller parts.
The PubSub component can use Tigase UserRepository to store it's data, then it is completely transparent to the kind of database you have. Whatever work with the main Tigase server, works with PubSub. However, this is not an optimal way to store PubSub data, therefore it can have own, dedicated schema, which is independent from the Tigase DB schema or even Tigase database.
I think such a separate is a good approach. You can develop and maintain PubSub independently from the Tigase code.
-
valid points. FWIW, i stared working on the migration of the mysql schema to postgres. got to admit though that i'm not the best-suited person for the job. do you have plans to do this? would it help to send you what i have?
thx for the hint regarding the user repository; guess that needs to be my temporary solution then.
Type |
Bug
|
Priority |
Blocker
|
Assignee | |
RedmineID |
784
|
i figured there is none for postgres after running into
can you please add it? the package becomes unusable in a postgres environment.