SQLite on development, MySQL on production?

Patrick McCafferty
Sat, 08 Oct 2005 18:13:32 -0000

Hi all,

Currently I''m using MySQL on my development machine and it works fine.
However, recently I''ve been trying to put together my tools on a USB
key so
that I can work on my project wherever I happen to be. So far I''ve
gotten
Eclipse set up with everything (svn and all) except the database.

The problem is that MySQL is *huge*. I have a few InnoDB tables (read: get
that MyISAM crap away from me) in my setup and to run all of those off my
USB key is just... bad. MySQL itself takes up a rather large amount of
space, and then the databases aren''t light either. This normally
isn''t a
problem, but when you''re working with about 384M and you want room for
stuff
besides the development environment it''s bad.

I''m looking into SQLite because it seems closer to what I want.
However, I''d
still like the option for using MySQL on my personal dev machine, as I
don''t
think there are too many GUI apps available for SQLite on OS X. A couple
problems I see with this are that the DDL for SQLite and MySQL are pretty
different, so it''s not a simple matter of dumping db/development.sql
into
SQLite to create the schema. But of course this problem will occur in
reverse as well - how do I keep this in sync without manually editing it
after a checkout? SQLFairy is something of an option except then I have to
carry Perl on my key as well.

Even if I move to SQLite on all my development machines I still have this
problem with deployment, since I''m definitely not going to use it for
production.

Any ideas?

Thanks.