https://bugzilla.wikimedia.org/show_bug.cgi?id=23741
--- Comment #4 from Happy-melon <[email protected]> 2010-06-01 18:54:20 UTC --- (In reply to comment #3) > I would think that users would prefer to have certain preferences set > globally, > especially when large checklists are involved, as might be the case with > interwiki search and watchlist options (see bug 3525). I thought about having > a > big two-dimensional checklist with preferences on one axis and wikis on the > other, and "select/deselect all" options for each row and column, but I think > on large wiki farms (e.g. Wikimedia) it would be too big to be manageable. Just make Special:Preferences set global prefs on the home wiki, and local prefs on other wikis. Only needs some good documentation and ghost indications of the default settings. > In order to help future-proof the database, perhaps we should just add a > "wiki" > field to all the tables, so that tables can be more readily shared without > causing a bunch of collisions. In cases where that field should be applicable > globally, it could be set to NULL or "*" as you suggest. There is a lot more > that needs to be done as far as cross-wiki integration is concerned, and I > think that this will create flexibility to implement such functionality > without > having to create new global tables and/or global databases. True, the field > would be useless in isolated wikis, but one never knows when one will want to > merge the wiki into a farm, e.g. to take a monolingual project multilingual. "having to create" new fields and databases is indeed a huge and difficult-to-organise operation. All the more reason *not* to do it except where it's genuinely needed. Adding fields willy-nilly purely for the sake of it or because it "might" be useful one day, is not intelligent coding, and will *not* make it into production code. > There might be some benefit, for instance, in having a wiki field for the page > table, so that templates could be shared across wikis by setting a "*" value > for that field. Changing the page on one wiki would change it on them all. > Although maybe an even better option would be put a foreign key in that field > leading to another table, and thereby provide arrays of wikis to which a given > setting applies. E.g., a preference, page, or whatever might apply only to > some > wikis but not others, rather being global. Sharing the page table is totally unrealistic; it has relational connections to twelve other tables which in turn connect to just about every other table in the database. For instance, "changing the page" requires creating a revision, which must be accessible to all wikis, because the revision record contains the link to the text table; equally the link tables such as imagelinks, for cache integrity. But the revision requires access to the user table, and imagelinks requires access to the image table; and the image table requires oldimage, and so on and so forth. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
