Database management in open source projects

Question

I was wondering how databases are managed in open source projects, which are usually hosted in repositories such as CVS or SVN. Placing codes in SVN is very logical, as it allows different team members to receive updated code snippets, but what about databases?

Are their schemas and contents (.sql files that I assume) hosted inside SVN? In this case, if I were creating a web application, would it require developers to continue updating their local databases with the latest .sql file?

Or is it more like having a central server whose members can change, and their software just plugs into the network?

I plan to launch an open source web application project (which requires a database), but I'm a little confused about how to handle the database management part.

Answer 1

In my experience, these types of applications typically include the database included in the assembly. Usually you need to install the database where you need, and then install the client. In addition, usually these databases are also open source, like MySQL or something like that.

Answer 2

Usually you include one or two things:

• Schema creation scripts
• Source data for uploading to the database

. - , , .

, , - - . , SQLite . .

Answer 3

, . , , . , , , , .

I would think that the most common option is that each developer uses their own database.

In either case, you will want to keep the schema creation and source data files in version control. Thus, all developers can easily create a new database.