> you must define every bit of a model in order for it to work. Rails is the opposite. ActiveRecord will ‘just work’ with the database. If you have an existing

> you must define every bit of a model in order for it to work. Rails is the opposite. ActiveRecord will ‘just work’ with the database. If you have an existing database, sure, Rails is preferred. If you're starting from scratch, the Django definitions can create the tables for you. If you do have existing tables though, you can use inspectDB to have Django create the models for you.