I agree with Aaron here, but suggest you worry more about using a
language/tools that allow you to write database independant code. Then you
can get going with your development on postgresql/mysql, and "upgrade" if
you find you need to later. With those numbers I really doubt you will
need to. I would still keep database independence in mind though. This may
or may not be easy to do, depending on the manguage you choose, and how
close you stick to standard SQL (ie don't use DB specidifc "features")
charles
On Thu, 27 Jan 2000, Aaron Turner wrote:
> My .02 for what it's worth:
>
> MySQL doesn't do transactions. For medical info this should in your mind
> take it out of the running. PosgresSQL is probably the slowest of the
> bunch, but has a good feature set and is very popular in the Linux
> community. For that few records, it should do quite well though.
>
> Oracle, is well Oracle. Kickass database able to do terabytes of data.
> Informix and Sybase are much closer to Oracle than Posgres.
>
> So, if you're looking for something powerful, cheap, and well supported in
> the community, I'd go PosgresSQL. If you're looking for something super
> powerful and commercial you might as well go all the way with Oracle.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
