Shahaf Abileah wrote:
I’m looking for a systematic way to document the schema for the
database behind our website (www.redfin.com http://www.redfin.com/),
so that the developers using this database have a better idea what all
the tables and columns mean and what data to expect. Any
On Tuesday 04 March 2008, Shahaf Abileah [EMAIL PROTECTED] wrote:
However, Postgres doesn't support the comment keyword. Is there an
alternative?
comment on table table_name is 'comment';
comment on column table.column_name is 'comment';
--
Alan
---(end of
I'm looking for a systematic way to document the schema for the database
behind our website (www.redfin.com http://www.redfin.com/ ), so that
the developers using this database have a better idea what all the
tables and columns mean and what data to expect. Any recommendations?
It would be
Shahaf Abileah wrote:
It would be great if the documentation could be kept as close to the
code as possible – that way we stand a chance of keeping it up to date.
So, in the same way that Java docs go right there on top of the class or
method definitions, it would be great if I could attach
Check http://www.postgresql.org/docs/8.3/interactive/sql-comment.html
Cheers!
Shahaf Abileah wrote:
I’m looking for a systematic way to document the schema for the database
behind our website (www.redfin.com http://www.redfin.com/), so that
the developers using this database have a better
