On 17 Jul 08:51, Dominique Chabord wrote: > > > Le 17/07/2014 01:47, Cédric Krier a écrit : > > On 17 Jul 00:57, Dominique Chabord wrote: > >> Le 16/07/2014 15:29, Cédric Krier a écrit : > >>> On 16 Jul 14:43, Dominique Chabord wrote: > >>>> Hello, > >>>> I think this option is required and should be defined per database and > >>>> not in configuration file. > >>> > >>> Soon it will be the same as one database per process. > >> > >> This is not a valid argument. If Tryton runs a single database at a > >> time, it can run several databases one after the other. > > > > Don't understand. > > > If you restore db_archive_A, save it, and then restore db-archive_B, you > donr'need to restart the server. This would become impossible.
You will have to restart. > This is off-topic, but single database would be uncompatible with > education requirements. Can not understand why education will need server provisioning in the ERP instead of general provisioning solution. > >> Nevertheless > >> will Tryton be single company too ? because this parameter is company > >> dependant. > > > > Tryton is already mainly single company, it is a fact see previous > > discussion about multi-company. > > I don't see any advantage to have multi-company if it is to have > > everything different. > > Here, I just apply the KISS principle. > > Multi-company is relevent in some cases, we can say we don't need to > address these use cases, but not just because we put company-related in > the config. OK. Let's try to use company and see if it doesn't cost too much. > >> And why is it different for other > >> company-related data ? > > > > What have you in mind? > Taxe rules, account plan, stock root etc... > > > >>> There will be more and more things going in the configuration file like > >>> the all ldap_connection module, the price digits etc. > >> > >> price digits and sum ordering are given accounting parameters of a > >> company. Two companies need different values. > > > > If two companies need different values, they should be managed by > > different instance. > > Today they just need two databases on the same instance. And tomorrow two instances which will lead to correct privilege separation. > >>>> Btw, if implemented in conf file, how would the history behave when > >>>> conf is changed ? or when database is restored ? > >>> > >>> People should be careful to not shoot their own foot. > >> > >> tryton must be manageable too. > > > > Exactly, that's why all those stuff should be in a configuration file. > > > >> For restoring any archive of a database > >> you will need to know about the configuration file of the original > >> server, adapt some parameters on your local server and start it. > > > > Yes and you will also need to know the version of the source code > > executed. > > Pypi works perfectly for this. Cutting and pasting in configuration > files is another story. Just like the attachment archive. -- Cédric Krier - B2CK SPRL Email/Jabber: [email protected] Tel: +32 472 54 46 59 Website: http://www.b2ck.com/
pgp4z6Rt0cBZR.pgp
Description: PGP signature
