While no one in thier right mind should be using wikipgedia, I'm sympathetic
to those who might still be stuck on it for some reason, so if you guys can
produce a patch against the wikipgedia cvs, I'd be happy to apply it.
I'd like to patch that name.
---(end of broad
On Friday 23 February 2007 16:43, Chad Wagner wrote:
> On 2/23/07, Bill Moran <[EMAIL PROTECTED]> wrote:
> > > In any case if anyone is interested I was able to reproduce the changes
> >
> > that
> >
> > > wikipgedia made and applied those changes (as well as others) all the
> >
> > way up
> >
> >
On 2/25/07, Magnus Hagander <[EMAIL PROTECTED]> wrote:
> For the record, anyone using wikipgedia deserves the pain they
> get: it is deprecated. The latest version of MediaWiki itself is what
> should now be used: it will detect if you have Postgres upon
> installation. :)
Perhaps the project s
On 2/25/07, Greg Sabino Mullane <[EMAIL PROTECTED]> wrote:
For the record, anyone using wikipgedia deserves the pain they
get: it is deprecated. The latest version of MediaWiki itself is what
should now be used: it will detect if you have Postgres upon
installation. :)
Some of us are still us
> For the record, anyone using wikipgedia deserves the pain they
> get: it is deprecated. The latest version of MediaWiki itself is what
> should now be used: it will detect if you have Postgres upon
> installation. :)
Perhaps the project should be *gasp* deleted then? ;-) Or is there
actual histo
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> How is the Postgres port of the Wikipedia doing this days anyway?
> Is it in a shape where one would consider it "competitive"?
The port of MediaWiki is going well: it is certainly usable, and
is already being used by a number of sites. I w
On 2/23/07, Bill Moran <[EMAIL PROTECTED]> wrote:
> In any case if anyone is interested I was able to reproduce the changes
that
> wikipgedia made and applied those changes (as well as others) all the
way up
> to the 1.6.10 codebase. The only reason I mention this is because 1.6is
> the only ch
Le vendredi 23 février 2007 16:37, Ian Harding a écrit :
> On 2/22/07, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> > Joshua D. Drake escribió:
> > > Andrej Ricnik-Bay wrote:
> > > > On 2/23/07, Jim Nasby <[EMAIL PROTECTED]> wrote:
> > > >> That depends greatly on what you're doing with it. Generall
On 2/22/07, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
Joshua D. Drake escribió:
> Andrej Ricnik-Bay wrote:
> > On 2/23/07, Jim Nasby <[EMAIL PROTECTED]> wrote:
> >> That depends greatly on what you're doing with it. Generally, as soon
> >> as you start throwing a multi-user workload at it, MySQL
In response to "Chad Wagner" <[EMAIL PROTECTED]>:
> On 2/23/07, Bill Moran <[EMAIL PROTECTED]> wrote:
> >
> > I installed wikipgdia for the WPLUG wiki:
> > http://wplug.ece.cmu.edu/wiki/
>
> Isn't that the same wikipgedia that is found at pgFoundry?
Yes.
> The only issue I
> really had the the
On 2/23/07, Bill Moran <[EMAIL PROTECTED]> wrote:
I installed wikipgdia for the WPLUG wiki:
http://wplug.ece.cmu.edu/wiki/
Isn't that the same wikipgedia that is found at pgFoundry? The only issue I
really had the the wikipgedia port is that the codebase is 1.6alpha, and it
seemed like it wa
Alvaro Herrera <[EMAIL PROTECTED]> wrote:
>
> Joshua D. Drake escribió:
> > Andrej Ricnik-Bay wrote:
> > > On 2/23/07, Jim Nasby <[EMAIL PROTECTED]> wrote:
> > >> That depends greatly on what you're doing with it. Generally, as soon
> > >> as you start throwing a multi-user workload at it, MySQL st
Alvaro Herrera wrote:
> Joshua D. Drake escribió:
>> Alvaro Herrera wrote:
>>> Joshua D. Drake escribió:
Andrej Ricnik-Bay wrote:
> On 2/23/07, Jim Nasby <[EMAIL PROTECTED]> wrote:
>> That depends greatly on what you're doing with it. Generally, as soon
>> as you start throwing a m
Joshua D. Drake escribió:
> Alvaro Herrera wrote:
> > Joshua D. Drake escribió:
> >> Andrej Ricnik-Bay wrote:
> >>> On 2/23/07, Jim Nasby <[EMAIL PROTECTED]> wrote:
> That depends greatly on what you're doing with it. Generally, as soon
> as you start throwing a multi-user workload at it,
Alvaro Herrera wrote:
> Joshua D. Drake escribió:
>> Andrej Ricnik-Bay wrote:
>>> On 2/23/07, Jim Nasby <[EMAIL PROTECTED]> wrote:
That depends greatly on what you're doing with it. Generally, as soon
as you start throwing a multi-user workload at it, MySQL stops
scaling. http://twea
Joshua D. Drake escribió:
> Andrej Ricnik-Bay wrote:
> > On 2/23/07, Jim Nasby <[EMAIL PROTECTED]> wrote:
> >> That depends greatly on what you're doing with it. Generally, as soon
> >> as you start throwing a multi-user workload at it, MySQL stops
> >> scaling. http://tweakers.net recently did a s
16 matches
Mail list logo
