Mailing List Archive: Bricolage: users

Postgres -> MySQL Upgrade Path?

Index | Next | Previous | View Threaded

waldo at vqronline

May 2, 2008, 9:03 AM

Post #1 of 6 (222 views)
Permalink

Postgres -> MySQL Upgrade Path?

Folks,

As I round third base in my transition to Bricolage here at VQR, I'm
excited by the news that 2.0 is coming out in July. Reading through
David's blog entry on the topic (via The Output Channel), some of
these features look like enormous improvements. The one that I'm
especially appreciative of us the implementation of Arsu Andrei's port
to MySQL, since I know how y'all PostgreSQL users feel about us MySQL
users. :)

Before I go any farther, though, I want to verify an assumption.
Surely users need to select between MySQL and PostgreSQL at install
time, and it won't be viable to switch (or upgrade, as I think of
it :) to MySQL on an existing installation. Right? Given how goofy our
web server setup is to accommodate Bricolage 1, I'm sorely tempted to
delay work on this upgrade until v2 comes out, at which time I'll wipe
the server and start anew, with mod_perl 2, Apache 2, PHP 5, MySQL 5,
etc. Does this makes sense to y'all?

BTW, we just won a National Magazine Award last night, though we were
beat out by National Geographic and Print for the other two Ellies we
were nominated for. I just thought I'd share. :)

Best,
Waldo

---
Virginia Quarterly Review
One West Range, Box 400223
University of Virginia
Charlottesville, VA 22904-4223

david at kineticode

May 2, 2008, 10:29 AM

Post #2 of 6 (213 views)
Permalink

Re: Postgres -> MySQL Upgrade Path? [In reply to]

On May 2, 2008, at 09:03, Waldo Jaquith wrote:

> Before I go any farther, though, I want to verify an assumption.
> Surely users need to select between MySQL and PostgreSQL at install
> time, and it won't be viable to switch (or upgrade, as I think of
> it :) to MySQL on an existing installation. Right?

Correct.

> Given how goofy our web server setup is to accommodate Bricolage 1,
> I'm sorely tempted to delay work on this upgrade until v2 comes out,
> at which time I'll wipe the server and start anew, with mod_perl 2,
> Apache 2, PHP 5, MySQL 5, etc. Does this makes sense to y'all?

Um, no? ;-P

> BTW, we just won a National Magazine Award last night, though we
> were beat out by National Geographic and Print for the other two
> Ellies we were nominated for. I just thought I'd share. :)

Congratulations! VQR is a cool magazine.

Best,

David

ktm at rice

May 2, 2008, 11:01 AM

Post #3 of 6 (208 views)
Permalink

Re: Postgres -> MySQL Upgrade Path? [In reply to]

On Fri, May 02, 2008 at 12:03:20PM -0400, Waldo Jaquith wrote:
> Folks,
>
> As I round third base in my transition to Bricolage here at VQR, I'm
> excited by the news that 2.0 is coming out in July. Reading through David's
> blog entry on the topic (via The Output Channel), some of these features
> look like enormous improvements. The one that I'm especially appreciative
> of us the implementation of Arsu Andrei's port to MySQL, since I know how
> y'all PostgreSQL users feel about us MySQL users. :)
>
> Before I go any farther, though, I want to verify an assumption. Surely
> users need to select between MySQL and PostgreSQL at install time, and it
> won't be viable to switch (or upgrade, as I think of it :) to MySQL on an
> existing installation. Right? Given how goofy our web server setup is to
> accommodate Bricolage 1, I'm sorely tempted to delay work on this upgrade
> until v2 comes out, at which time I'll wipe the server and start anew, with
> mod_perl 2, Apache 2, PHP 5, MySQL 5, etc. Does this makes sense to y'all?
>
I have a couple of comments. First, if you are already using PostgreSQL with
Bricolage, it does not make sense to me to move to the MySQL backend. Among
other things, MySQL does not support full-text indexing yet with the InnoDB
backend and there is a Google SoC project to add full-text indexing support
to Bricolage. If however, you do not have any PostgreSQL DBA expertise then
it really is not much of a decision for you. Good luck with what ever path
you choose. Like you, I am looking forward to the Apache 2 support.

Cheers,
Ken

waldo at vqronline

May 2, 2008, 11:06 AM

Post #4 of 6 (214 views)
Permalink

Re: Postgres -> MySQL Upgrade Path? [In reply to]

Ken,

On May 2, 2008, at 2:01 PM, Kenneth Marshall wrote:
> I have a couple of comments. First, if you are already using
> PostgreSQL with
> Bricolage, it does not make sense to me to move to the MySQL
> backend. Among
> other things, MySQL does not support full-text indexing yet with the
> InnoDB
> backend and there is a Google SoC project to add full-text indexing
> support
> to Bricolage. If however, you do not have any PostgreSQL DBA
> expertise then
> it really is not much of a decision for you. Good luck with what
> ever path
> you choose. Like you, I am looking forward to the Apache 2 support.

I honestly know nothing at all about PostgreSQL, so I'll likely follow
your recommendation. Just last week I decided to get into the
Bricolage DB and poke around, just to see how it's structured. It took
me a good ten minutes to figure out the command line arguments to use
to open up the database in Postgres, and I never did figure out how to
list the tables, view the table structure, etc. I've been developing
in MySQL for nine years. PostgreSQL:MySQL::Spanish:French, I think --
similar, but different enough that my head is spinning. :) Thanks for
the advice, Ken!

Best,
Waldo

---
Virginia Quarterly Review
One West Range, Box 400223
University of Virginia
Charlottesville, VA 22904-4223

david at kineticode

May 2, 2008, 11:23 AM

Post #5 of 6 (205 views)
Permalink

Re: Postgres -> MySQL Upgrade Path? [In reply to]

On May 2, 2008, at 11:06, Waldo Jaquith wrote:
>
> I honestly know nothing at all about PostgreSQL, so I'll likely
> follow your recommendation. Just last week I decided to get into the
> Bricolage DB and poke around, just to see how it's structured. It
> took me a good ten minutes to figure out the command line arguments
> to use to open up the database in Postgres, and I never did figure
> out how to list the tables,

\dt

> view the table structure

\d usr

> , etc.

\?

Best,

David

jean-michel.caricand at laposte

May 2, 2008, 11:36 AM

Post #6 of 6 (211 views)
Permalink

Re: Postgres -> MySQL Upgrade Path? [In reply to]

> Message du 02/05/08 20:24
> De : "David E. Wheeler" <david[at]kineticode.com>
> A : users[at]lists.bricolage.cc
> Copie à :
> Objet : Re: Postgres -> MySQL Upgrade Path?
>
> On May 2, 2008, at 11:06, Waldo Jaquith wrote:
> >
> > I honestly know nothing at all about PostgreSQL, so I'll likely
> > follow your recommendation. Just last week I decided to get into the
> > Bricolage DB and poke around, just to see how it's structured. It
> > took me a good ten minutes to figure out the command line arguments
> > to use to open up the database in Postgres, and I never did figure
> > out how to list the tables,
>
> \dt
>
> > view the table structure
>
> \d usr
>
> > , etc.
>
> \?
>
> Best,
>
> David
>

You can also use PgAdmin. It's a good GUI application.

> - Jean-Michel

Créez votre adresse électronique prénom.nom[at]laposte.net
1 Go d'espace de stockage, anti-spam et anti-virus intégrés.

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com