All,
Having done some comparison of both mySQL and PostgreSQL, I would
STRONGLY recommend that you have a look at Interbase SQL Server
(www.interbase.com).
- it supports 98% of possible OS's (NT, Linux, Unix...)
- it is a true SQL server (with transactions, triggers, Stored
Procedures, referential integrity)
- has a unique concurrency model which allows readers NEVER to block
writters.
- has been around for 15 years (it's used by US Army for the M1 tank and
a host of others)
- recently announced it's release as open source (it's not yet released
but should be very, very soon).
I have been using it for 3+ years and found it to be great with
excellent community (much like this list).
Sean
> -----Original Message-----
> From: Mike Bannister [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 29, 2000 6:46 PM
> To: [EMAIL PROTECTED]
> Subject: RE: MySQL on UNIX w/ CF on NT4
>
>
> We are using this for a multi-user 'portal-like' site for a
> large *.EDU. If
> it is successfull it will be very high traffic.
>
> If it doesn't support transactions what exactly does that
> mean and how might
> it cause problems?
>
> If you can't do subqueries that would mean running many extra
> SQL queries
> and a heck of a lot of code to make them relate data the way a normal
> relational database might right?
>
> Anyone else around that has experience with MySQL, please any
> thought on how
> it might react in such a multiuser environment would be helpful.
>
> Thanks!
>
> Mike Bannister
> geekteam.com
>
> -----Original Message-----
> From: Mike [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 29, 2000 5:35 PM
> To: [EMAIL PROTECTED]
> Subject: Re: MySQL on UNIX w/ CF on NT4
>
>
> Lots of comments on these questions here:
>
> http://slashdot.org/articles/00/06/28/1454220.shtml
>
> I'm no expert, but my impressions:
>
> a. MySQL recently supports transactions. I don't know if
> this support is
> in a current 'stable' release yet or not.
>
> b. You can't do sub-queries.
>
> c. Locking mechanisms are pretty weak.
>
> The consensus seems to be that MySQL is built for speed and not for
> situations where you need rock-solid data integrety. So if
> you're serving
> dynamic web content, MySQL is great. For a sales processing
> database you
> might want to look at something like Postgres.
>
>
> At 04:55 PM 6/29/00 -0400, you wrote:
> >Hello,
> >
> >We are about to start a fairly large project using mysql on Unix
> >as our DB. I hear there is no transaction support, you can't do
> >'sub selects' (Is that the same thing as a sub-query?), and
> that it is
> >in some way 'single threaded' and/or unsuitable for multiuser
> >environments...?
> >Could someone with some experience explain/clarify these things and
> >possibly provide some examples of where we might run into trouble...?
> >
> >Thanks in advance for any help you can offer.
> >
> >Mike Bannister
> >geekteam.com
> >
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
