Hi Henning,
It is about DB re-organizing, I think it was a good point Klaus made
some time ago - all the tables should have a prefix identifying the
module they belong to. Right now there are tens of tables and for some
of them you do not have any clue what module is using them.
So, there are 3 directions here:
1) renaming the tables (adding a prefix of fix len)
2) to be able to configure what tables should be installed (we have
the core, presence, extra - right now, but something for details would
be good - maybe based on modules ?)
3) what Henning suggested - have a general description of DB and
some tools to generate particular DB definitions for mysql, postgres,
dbtext, etc..
regards,
bogdan
Henning Westerholt wrote:
On Freitag, 11. Mai 2007, Juha Heinanen wrote:
> I would like to hear your opionion on this, as this is a central part of
> OpenSER. If nobody objects, i plan to start to work next week on
> this.
sounds good to me. perhaps there could also be a configuration file
where one could tell, which tables need to be installed in an individual
openser setup. i, for example, use only a small subset of openser
tables, because of radius.
Hi Juha,
i plan to split the tables, e.g.: the "core table" into acc, aliases,
dbaliases, grp etc.. and make the whole process modular. Then this should be
possible.
Cheers,
Henning
_______________________________________________
Devel mailing list
Devel@openser.org
http://openser.org/cgi-bin/mailman/listinfo/devel
_______________________________________________
Devel mailing list
Devel@openser.org
http://openser.org/cgi-bin/mailman/listinfo/devel
