# Mac OS X Leopard DBMS **URL:** \ **Category:** Rails\ **Created:** [October 27, 2007, 9:12pm UTC](https://www.ruby-forum.com/t/mac-os-x-leopard-dbms/118494 "2007-10-27T21:12:04Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![rawn027](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/d07c76/32.png) [@rawn027](https://www.ruby-forum.com/u/rawn027)\ **Post date:** [October 27, 2007, 9:12pm UTC](https://www.ruby-forum.com/t/mac-os-x-leopard-dbms/118494/1 "2007-10-27T21:12:04Z")
What is the best choice of DBMS for Rails on Mac OS X. This is quite annoying that it was not shipped by default because they have a full rails development stack without mysql or postgresql. I hope they didnt feel that SQLite was the DBMS of choice. It doesnt even support foreign keys! -Ron ---
**Author:** ![rawn027](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/d07c76/32.png) [@rawn027](https://www.ruby-forum.com/u/rawn027)\ **Post date:** [October 27, 2007, 9:24pm UTC](https://www.ruby-forum.com/t/mac-os-x-leopard-dbms/118494/2 "2007-10-27T21:24:21Z")
On Oct 27, 2007, at 3:10 PM, Ronald V. wrote: > What is the best choice of DBMS for Rails on Mac OS X. This is quite > annoying that it was not shipped by default because they have a full > rails development stack without mysql or postgresql. > > I hope they didnt feel that SQLite was the DBMS of choice. It doesnt > even support foreign keys! SQLite is a great database to start developing a rails application with. ActiveRecord will enforce your foreign key integrity. Some Rails applications deviate from the basic “data in, data out” pattern, and eventually you can use the more advanced features of a database like MySQL or PostgreSQL, such as MySQL’s full text search, or Postgres’ indexed calculations. But the more you can rely on ActiveRecord, the easier things are to test and maintain. Alternatively, you can get MySQL from [mysql.com](http://mysql.com), and it works great on Leopard, or at least it does for me so far. Do note that even though MySQL has support for foreign key constraints, many people still choose to leave that up to ActiveRecord. ---
**Author:** ![rawn027](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/d07c76/32.png) [@rawn027](https://www.ruby-forum.com/u/rawn027)\ **Post date:** [October 27, 2007, 9:29pm UTC](https://www.ruby-forum.com/t/mac-os-x-leopard-dbms/118494/3 "2007-10-27T21:29:02Z")
How do I go about using ActiveRecord to enforce foreign key integrity compared to doing that traditionally on the DBMS? Thanks. -Ron