Sean,

Thanks for the information. I'm developing a desktop application
that requires an embedded database. Therefore I'm attracted to
Firebird because:

1. It appears to have been built from the groundup keeping embedded
applications in mind.

2. It is much more mature than MySQL, handling referential
integrity, transactions and user defined functions in it's current
stable production release.

3. Commercial applications can embed Firebird royalty free. Correct
me if I'm wrong here.

Thanks again,
Kevin Morris

--- In ib-support@y..., "Leyne, Sean" <sleyne@a...> wrote:
> Kevin,
>
> > Does anyone know of a tool which could convert a MySQL schema
and
> > data dump (in the form of DDL and INSERT statements) into
Firebird
> > compatible SQL? Specifically, I'd like autoincrement fields
> > converted to generators and triggers. I know this is fairly
easy to
> > do by hand, but I need to do it repeatedly while we transition
from
> > MySQL to FB.
>
> I would suggest that you take this task and break it up into 2
steps.
>
> The first would be to migrate your MySQL schema to Firebird.
Given what
> I know of MySQL, you would be advised to extract it to a text file
and
> edit the file to suit your (Firebird) needs/requirements.
>
> The second step would be to move the data. For this I would
suggest
> using a freeware tool called IBDataPump
(www.clevercomponents.com). The
> tool allows you to move data into a Firebird database, from both an
> existing database but also from a BDE/ODBC/ADO datasource. I use
it a
> lot to migrate data between database as we update/upgrade our
> application database schema.
>
> Using this approach you can create and refine your Firebird
database and
> then pump the data as required to test our work application.
>
>
> Sean
>
> P.S. It's nice to hear that your moving from MySQL, the start of a
> trend I hope ;-) What attracted you to Firebird?