[ale] So many choices....

[Russell Enderby]

I have been using MySQL and it runs like a champ.  I have not used PostgresQL
like Damien so I cannot give you pluses or minues.  I do know that MySQL was
written for huge database sizes and running extremely fast.  So it sounds like
that is right down your alley.
Russell

Chris Ricker wrote:

> Hi all,
>
> I'm starting to amass a large amount of data, and I'd like to create a db to
> hold it since my current solution of papers stuffed in lab notebooks doesn't
> really scale ;-).  The size probably won't get that insane--maybe 900 rows,
> 600 columns, each cell ~500 chars for the main table.
>
> The relationships between my data points aren't that complex, so I don't
> need ACEDB or anything like that.  I'm mainly just planning on storing the
> data, obviously, and then doing the usual PHP -> web with some of it, so I
> was thinking either MySQL or PostgresQL.  Anyone want to comment on the
> relative merits of those two (ie, why I would choose one over the other)?
> Any other suggestions?
>
> thanks,
> chris
>
> --
> Chris Ricker                                               kaboom at gatech.edu
>                                               chris.ricker at genetics.utah.edu



--
Russell T. Enderby                                        Arris Interactive
Software Engineer                                         3871 Lakefield Dr,
Suite 300
Cornerstone Software Development Group   Suwanee, GA 30024-1242
Email: Russell.Enderby at arris-i.com