[Wikitech-l] Store IP using varchar(40) is enough?

According to this: http://www.mediawiki.org/wiki/Manual:User_newtalk_table, IP was stored using varchar(40) . But seems 45 should be the safe instead of 39? http://stackoverflow.com/questions/4982701/best-way-to-store-ip-in-database ___ Wikitech-l

[Wikitech-l] fss_prep_replace implemented in Python/Perl

I an not sure if it is the right place to ask this. I got the source of fss_prep_replace at http://opensees.berkeley.edu/wiki/extensions/FastStringSearch/fss.c But are there any Perl or Python implementations? Thanks. ___ Wikitech-l mailing list

Re: [Wikitech-l] varchar(255) binary in tables.sql

Hi, On Mon, Jun 7, 2010 at 1:36 AM, Platonides platoni...@gmail.com wrote: No. The BMP problem is only present with the MySQL 4.1/5.0 UTF-8 option. It seems 5.0 and 5.1 support for UTF-8 are the same http://dev.mysql.com/doc/refman/5.0/en/charset-unicode.html

Re: [Wikitech-l] varchar(255) binary in tables.sql

Hello, On Sun, Jun 6, 2010 at 11:12 PM, Platonides platoni...@gmail.com wrote: MediaWiki supports both ways. Wikipedia still uses the mysql 4 compatible options, and since mysql chars only support the bmp, it isn't likely to change. It all depends on what you choose on install. Currently, the

[Wikitech-l] varchar(255) binary in tables.sql

Hello all, I remember in old days, UTF-8 string are stored as varbinary, are there reason to change to varchar(255) binary? Also, what is the default server/connection/client character set settings now? Thanks. ___ Wikitech-l mailing list

Re: [Wikitech-l] Bugzilla Vs other trackers.

On Thu, Jan 7, 2010 at 11:22 PM, Bryan Tong Minh bryan.tongm...@gmail.com wrote: I would prefer something that would tightly integrate with CodeReview, but that probably means writing custom software, which is a lot of work. I think atlassian is happy to provide Jira as well as other tools for

Re: [Wikitech-l] Size of DB/table of enwiki after import into MySQL

On Fri, Nov 27, 2009 at 6:58 AM, Aryeh Gregor simetrical+wikil...@gmail.com wrote: On Thu, Nov 26, 2009 at 8:29 AM, Ryan Chan ryanchan...@gmail.com wrote: so what are your suggestion? use Java? Python! In what aspect? Just another scripting language

Re: [Wikitech-l] Size of DB/table of enwiki after import into MySQL

On Thu, Nov 26, 2009 at 12:23 AM, Greg Sabino Mullane g...@endpoint.com wrote: Frankly, the choice of using PHP as the language for MediaWiki has probably caused more problems over the years than the choice of database backend. :) so what are your suggestion? use Java?

Re: [Wikitech-l] Size of DB/table of enwiki after import into MySQL

On Mon, Nov 23, 2009 at 12:26 AM, Aryeh Gregor simetrical+wikil...@gmail.com wrote: On Sat, Nov 21, 2009 at 10:40 PM, Ryan Chan ryanchan...@gmail.com wrote: Is the source available in the svn? Can you point me to the right direction? http://svn.wikimedia.org/viewvc/mysql/ Thanks

Re: [Wikitech-l] Size of DB/table of enwiki after import into MySQL

On Sun, Nov 22, 2009 at 7:39 AM, Aryeh Gregor simetrical+wikil...@gmail.com wrote: It's also worth pointing out that Wikipedia uses a version of MySQL with substantial modifications, Is the source available in the svn? Can you point me to the right direction? Thanks.

Re: [Wikitech-l] Size of DB/table of enwiki after import into MySQL

On Sat, Nov 21, 2009 at 12:05 PM, Q overlo...@gmail.com wrote: MediaWiki has used MySQL since the beginning and has let the code get away with things that shouldn't have been done which makes switching to Postgres hard. Isn't that mediawiki also support pgsql?

[Wikitech-l] Wikipedia Test, Build Deploy practices

Hello, Just out of curiosity, now consider if a security hole in mediawiki was identified, how does wikipedia manage to roll out the new patch to all servers? Any formal steps? Tesing? Regression? UAT? Any build/deployment scripts can be shared? Thanks.