Tim Starling writes:
> A new user preference has been added, allowing the user to specify
> their gender.
Be sure to also mention how to disable interrogating users' gender.
Please implement 'Allow not asking users their gender'
https://bugzilla.wikimedia.org/show_bug.cgi?id=18761
___
Exactly. Using wgDbType outside of the database should
never be necessary.
-Chad
On May 16, 2009 12:59 PM, "Roan Kattouw" wrote:
2009/5/16 Freako F. Freakolowsky :
> Why was this approach opposed? > I am working on Oracle abstraction at the
moment and i was planni...
What I think DJ Bauch mean
2009/5/16 Jan Luca :
> Hello,
>
>
>
> how can I create a log?
>
Do you just want to add a log entry, or do you want to add an entirely
new log type? In the latter case, look at $wgLogTypes [1], for the
former look at the LogPage class [2]. For example usage, look at
extensions which add logs, such
2009/5/16 Freako F. Freakolowsky :
> Why was this approach opposed?
> I am working on Oracle abstraction at the moment and i was planning to
> implement such a function.
>
> DJ Bauch wrote:
>> I would much rather see a function added at the Database
>> class level to form compound queries from subq
I use this to make a log:
Initialize log page:
$wgLogTypes[] = 'newlog';
$wgLogNames['newlog'] = 'newloglogpage';
$wgLogHeaders['newlog']= 'newloglogpagetext';
$wgLogActions['newlog/newlog'] = 'newloglogentry';
Add new log entry:
//Log it
$log =
Hello,
how can I create a log?
Gruß
Jan
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Why was this approach opposed?
I am working on Oracle abstraction at the moment and i was planning to
implement such a function.
DJ Bauch wrote:
> I would much rather see a function added at the Database
> class level to form compound queries from subqueries, since the
> alternative is to introdu
On Sat, May 16, 2009 at 2:21 AM, Domas Mituzas wrote:
> George,
>
> > Eventually, supportability and bugfixes for newer versions surpass
> > those for
> > older versions.
>
> True, though we don't hit bugs too much in 4.0, it is somewhat
> rocksolid for us.
> Eventually not going for 5.4 will be b
George,
> Eventually, supportability and bugfixes for newer versions surpass
> those for
> older versions.
True, though we don't hit bugs too much in 4.0, it is somewhat
rocksolid for us.
Eventually not going for 5.4 will be bad situation (once innodb plugin
1.0.3 features get merged in, e.
Hoi,
An upgrade to MySQL 6 would make a big difference for language and collation
support. We need to first make use of improvements that are out there before
we consider "roling our own".
Thanks,
GerardM
2009/5/16 Bart
> MySQL is open source -- what sort of changes did you have in mind?
Hoi,
There are several parts to that question. Typically you upgrade for the
benefit of new functionality, security fixes and performance improvements.
These are all sound reasons why we should upgrade. Reasons why not to
upgrade are prerequisites for the upgrade are not in place, the logistics of
* Aryeh Gregor [Fri, 15 May 2009
13:55:22 -0400]:
> Wikimedia is nowhere *close* to the largest MySQL user. It's a
> mid-sized MySQL user at most. It's one of the largest *websites*
> using MySQL, but there are data warehouses and whatnot that have
> vastly larger databases, and definitely more
12 matches
Mail list logo
