MySQL is probably not a good choice.

Most flavors of MySQL do not have a two phase commit (potential for data
integrity issues). Firebird does have two phase commit, so your data is
safer.

One of our vendors for a 24x7 high volume service uses MySQL for their
front end database ... and the thing is always going down for
unexplained reasons. We have even lost data when their server failed
silently. Firebird does not fail silently, you know when something is
broken.

You may want to look at Java for high volume work - the Delphi tools
that I tested were, for the most part, borderline once you got over
about a thousand transactions per second. The JDBC model is a bit more
robust in heavy processing models than the pure Delphi model.

IBObjects was the only Delphi option that passed my tests, but it was
also the least "borland like" of the tools I tested.

Good luck!

On Fri, 2005-02-18 at 03:12, Jannie Nel wrote:
>
>
> >>What problems are you having?
> >>Alot of companies use firebird for even larger volumes of data than
> >>you are describing.
>
> Hi Dalton,
>
> We are looking at open source databases for an upcoming project. They
> will require fairly extensive search capabilities on person information
> - by area, street, etc.
>
> My other option so far would be MySQL, but because we are a Delphi shop,
> I'd prefer FireBird.
>
> Jannie.
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>