Re: Thoughts on comments
Date: Fri, 22 Mar 2013 14:06:29 +0200
Message-ID: <CAN2wOq1zNyCdBNiL0vMtLqvof_Trry68_+oxV7ugJF0NA56kFg_at_mail.gmail.com>
BTW I have experienced quite a few cases when initially (logical) data model (ER diagram, class model, whatever tool) has been created and initially everything is in data model. But after a time (months, years) changes are being made in DB, but never synchronised with data model. So in these cases comments in DB can really help. Of course there is always possibility to reverse engineer DB and create physical data model diagram, but it won't help much in case of cryptic table, column names. And even more in cases when FKes are managed in application.
Gints
2013/3/22 Jeff Smith <jeff.d.smith_at_oracle.com>
> If you keep them in the data model, you assume that everyone has a copy
> of the data model.
>
> If you put them in the database, then folks using your database will
> have access to your comments.
>
> I prefer both - write at design time in your data model, and also
> include in your database objects. I've had to help too many end users
> with poorly documented systems to rely on having a good data model around.
>
> Jeff
>
> On 3/22/2013 12:25 AM, z b wrote:
> > Listers,
> >
> > Just wanted to get a general opinion on using comments in the
> > database. For example COMMENT ON COLUMN table.column "No comment".
> >
> > Does anyone do this as a regular best practice? I would prefer to see
> > this abstraction in a data model, maybe not pushed to the database
> > layer, especially since not all RDBMS engines have "comment"
> > functionality.
> >
> > The thought is we should do this for every column, every table, every
> > oracle db. This ends up being several million comments added to the
> > our various instances.
> > --
> > http://www.freelists.org/webpage/oracle-l
> >
> >
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>
-- http://www.freelists.org/webpage/oracle-lReceived on Fri Mar 22 2013 - 13:06:29 CET