Hi Mike,
What I was worried about was not the prefixing, but rather that MW would someday change the schema to include a table called tableEditTableName, to use your example. The probability of this happening is admittedly low, but is higher for the possible names that are most obvious in describing the functions of the tables. If the TableEdit extension became really popular, then the devs would probably know not to clash with it, but I'm assuming that it's not widely used at this point and they might hit a namespace clash by accident with no malicious intent.
Of course, the MW devs are too smart to do what I did, and give a table a field name that is also a mysql reserved word!
Jim
On Jul 28, 2007, at 5:27 PM, Michael Daly wrote:
Jim Hu wrote:
But it seems like that was a bad idea, especially if one wants two instances on the same mysql server... which I discovered I do want.
You have, I think, the info you need to create a table within the local Wiki database. $wgDBserver, $wgDBname, $wgDBuser and $wgDBpassword gets you into the database and
$wgDBprefix
will tell you which unique DB prefix is used for multiple wikis. Therefore, you can create a table with the name of $wgDBprefix.tableEditTableName and even if the user has two instances in the same MySQL, it will not conflict.
Mike
MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
===================================== Jim Hu Associate Professor Dept. of Biochemistry and Biophysics 2128 TAMU Texas A&M Univ. College Station, TX 77843-2128 979-862-4054