It's an alternative solution. We had to choose one. Florent
On Fri, Aug 12, 2011 at 2:32 PM, Sean Radford <[email protected]> wrote: > But upgrades often require table re-structuring (columns added and taken > away). > > As long as you are happy that this is a robust solution going forward, then > that's fine (though I'm not convinced). > > Regards, > > Sean > > > On 12/08/11 12:59, Florent Guillaume wrote: >> >> It was chosen because it doesn't imply any changes in the user table >> format. >> >> >> On Thu, Aug 11, 2011 at 3:37 PM, Sean Radford<[email protected]> >> wrote: >>> >>> I did think that you could use a Multi-Directory, but: >>> >>> 1. That doesn't seem very scalable to me. >>> 2. There is the problem of getting the database to ensure uniqueness >>> across >>> the different tables. >>> >>> Does anyone know, the rationale for opting for this >>> table-per-configuration >>> approach? I do seem to recall Florent mentioning the use of the >>> column-discriminator design in the past, so wondering why this >>> alternative >>> was chosen. >>> >>> Regards, >>> >>> Sean >>> >>> >>> On 11/08/11 10:16, Thomas Roger wrote: >>>> >>>> Hi, >>>> >>>> To avoid having a context document for login, you should use a >>>> MultiDirectory that wraps all the user directories, and do the >>>> authentication against it. >>>> Be aware that a user id should be unique across the different user >>>> directories. >>>> >>>> -- >>>> Thomas >>>> >>>> >>>> >>>> On 11 August 2011 09:18, Sean Radford<[email protected]> wrote: >>>>> >>>>> Hi, >>>>> >>>>> Been reading about the Local Configuration Directory Service >>>>> >>>>> >>>>> (http://blogs.nuxeo.com/dev/2011/06/new-local-configuration-directory-service-first-step.html) >>>>> and looking at the 5.4.3-SNAPSHOT source (in particular the >>>>> UserManagerImpl >>>>> that is the start of the multi tenant functionality). >>>>> >>>>> From my understanding, when a directory is opened, the actual >>>>> underlying >>>>> table that is used depends on the DirectoryLocalConfiguration of the >>>>> Document in context. I can see how this works for vocabularies, but for >>>>> users is there not an issue at login as there is never any Document in >>>>> context and so you always query the same table for your user. >>>>> >>>>> Or am I missing something? >>>>> >>>>> Would it not be better to have an additional column in each directory >>>>> table >>>>> denoting the DirectoryLocalConfiguration value with all queries having >>>>> the >>>>> relevant value appended as an additional WHERE clause? You could then >>>>> have a >>>>> 'special case' context document to denote querying across all >>>>> DirectoryLocalConfigurations for the login situation. >>>>> >>>>> Regards, >>>>> >>>>> Sean >>>>> >>>>> -- >>>>> Dr. Sean Radford, MBBS, MSc >>>>> http://www.tacola.com/ >>>>> http://www.tacolaecm.com/ >>>>> t: +44 (0)845 KEY HELP >>>>> t: +44 (0)845 539 4357 >>>>> m: +44 (0)7802 24 24 86 >>>>> >>>>> --- >>>>> Mailing list: [email protected] >>>>> Forum: http://forum.nuxeo.org/f/1/ >>>>> >>> >>> -- >>> Dr. Sean Radford, MBBS, MSc >>> http://www.tacola.com/ >>> http://www.tacolaecm.com/ >>> t: +44 (0)845 KEY HELP >>> t: +44 (0)845 539 4357 >>> m: +44 (0)7802 24 24 86 >>> >>> --- >>> Mailing list: [email protected] >>> Forum: http://forum.nuxeo.org/f/1/ >>> >> >> > > > -- > Dr. Sean Radford, MBBS, MSc > http://www.tacola.com/ > http://www.tacolaecm.com/ > t: +44 (0)845 KEY HELP > t: +44 (0)845 539 4357 > m: +44 (0)7802 24 24 86 > > -- Florent Guillaume, Director of R&D, Nuxeo Open Source, Java EE based, Enterprise Content Management (ECM) http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87 --- Mailing list: [email protected] Forum: http://forum.nuxeo.org/f/1/
