Rules of Database App Aging - Push cx
http://push.cx/2009/rules-of-database-app-aging

"all fields become optional" etc. good stuff.

Rule 3. (too true!) Chatter Always Expands

This will be incomprehensible to non developers in the audience, but oh god, this is so painfully, painfully true.

"I mentioned I’ve learned some rules of how database apps change over time, now that I’ve done a few dozen. They are: ... "

Visual relational database designer, done entirely in <canvas> and javascript. Rather swanky-looking.

This tool allows you to draw and create database schemas (E-R diagrams) directly in browser, without the need for any external programs (flash)

JSONスキーマ

All successful standards are as simple as possible, not as hard as possible.

joes

Orderly is a textual format for describing JSON. Orderly can be compiled into JSONSchema. It is designed to be easy to read and write.

Orderly is a textual format for describing JSON. Orderly can be compiled into JSONSchema. It is designed to be easy to read and write. JSONSchema attempts to provide a representation for three distinct types of information about JSON structures: * Data structure (for documentation and validation purposes) * Storage attributes (information pertinent to tools that wish to persist JSON data) * Interaction Control (providing hints on how to render a UI where data can be manipulated). JSONSchema attempts to provide a representation for three distinct types of information about JSON structures: * Data structure (for documentation and validation purposes) * Storage attributes (information pertinent to tools that wish to persist JSON data) * Interaction Control (providing hints on how to render a UI where data can be manipulated).

Migrations bother me. On one hand, migrations are the best solution we have for the problem of versioning databases. The scope of that problem includes merging schema changes from different developers, applying schema changes to production data, and creating a DRY representation of the schema. But even though migrations is the best solution we have, it still isn’t a very good one.

Check the brainstorming at the end. I love where he's going. Short version: a schema.yml file identified by its SHA1 hash. Migrations are for translating data between versions. Great comments at the end by the smart people in the community.

On one hand, migrations are the best solution we have for the problem of versioning databases. The scope of that problem includes merging schema changes from different developers, applying schema changes to production data, and creating a DRY representation of the schema.