It seems new datamodel scripts are required for each back-end database. Since it may not be possible to have 1 script in generic SQL that will work across all databases, has anyone considered maintaining the datamodel through a UML tool and then using various code-generator templates to generate appropriate SQL DDL per-database? One fringe-benefit of this approach would be the ability to visualize the current datamodel by exporting the UML digram into a graphic file.
Date: Wed, 13 Jul 2005 23:18:00 +0100 From: Kate keturner@livejournal.com Subject: [Wikitech-l] Oracle support To: mediawiki-l@mail.wikimedia.org, wikitech-l@mail.wikimedia.org
hi,
for those interested, i have begun adding support for Oracle database backend to 1.5, in a separate branch. at present it's somewhat usable (editing mostly works), but many things are unimplemented or broken. to check out a copy of the source:
cvs -d :pserver:anoncvs@cvs.defau.lt:/root login
(press enter for password)cvs -d :pserver:anoncvs@cvs.defau.lt:/root co
-rORACLE_WORK phase3
there's no installer support, so you'll need to create a LocalSettings.php manually (easiest is to install it under MySQL and copy the file). set $wgDBserver to any non-empty string, $wgDBtype to 'oracle' and $wgDBname to your Oracle SID. run "@maintenance/oracle/tables.sql" from SQLPlus to import the table definitions. to make a user into a sysop after installation:
SQL> CALL add_user_right('Username', 'sysop') SQL> CALL add_user_right('Username', 'bureaucrat')
please file bugs related to Oracle support in bugzilla, blocking #652.
kate.
__________________________________ Yahoo! Mail Stay connected, organized, and protected. Take the tour: http://tour.mail.yahoo.com/mailtour.html