Added to TODO:
* Allow COMMENT ON to accept an expression rather than just a
string
---
Michael Glaesemann wrote:
> I've been trying to be better at documentation in general and have
> been trying to t
On Nov 24, 2005, at 12:29 , Andrew Dunstan wrote:
Michael Glaesemann said:
On Nov 24, 2005, at 12:02 , Andrew Dunstan wrote:
To change this would involve changing the grammar.
I thought it might—and am thinking it might be all that would need
changing.
No, you'd have to have code to g
Michael Glaesemann said:
>
> On Nov 24, 2005, at 12:02 , Andrew Dunstan wrote:
>
>> To change this would involve changing the grammar.
>
> I thought it mightand am thinking it might be all that would need
> changing.
>
No, you'd have to have code to get the expression evaluated.
cheers
andrew
Thanks for the feedback, Andrew.
On Nov 24, 2005, at 12:02 , Andrew Dunstan wrote:
To change this would involve changing the grammar.
I thought it might—and am thinking it might be all that would need
changing.
You could possibly write a stored proc that manipulated pg_description
direct
To change this would involve changing the grammar.
You could possibly write a stored proc that manipulated pg_description
directly.
cheers
andrew
Michael Glaesemann said:
> I've been trying to be better at documentation in general and have
> been trying to take advantage of PostgreSQL's COMMEN
I've been trying to be better at documentation in general and have
been trying to take advantage of PostgreSQL's COMMENT ON
functionality to provide a little more information in the DDL itself.
I usually write my DDL in a text file and load it into the database
using psql. To make it (a lit
