<div dir="ltr"><br /><br />On Wed, Oct 8, 2014 at 12:36 AM, Josh Berkus <<a
href="mailto:josh@agliodbs.com">josh@agliodbs.com</a>>wrote:<br />><br />> On 10/07/2014 09:44 AM, Fabrízio de
RoyesMello wrote:<br />> > We can think in a mechanism to create "properties / options" and assign it<br />>
>to objects (table, index, column, schema, ...) like COMMENT does.<br />> ><br />> > A quickly
thought:<br/>> ><br />> > CREATE OPTION [ IF NOT EXISTS ] name<br />> > VALIDATOR valfunction<br
/>>> [ DEFAULT value ];<br />> ><br />> > ALTER TABLE name<br />> > SET OPTION optname
{TO | = } { value | 'value' | DEFAULT };<br />> ><br />> > It's just a simple thought of course. We must
thinkbetter about the syntax<br />> > and purposes.<br />><br />> If we're going to do this (and it seems
likea good idea), we really,<br />> really, really need to include some general system views which expose<br />>
theoptions in a user-friendly format (like columns, JSON or an array).<br />> It's already very hard for users to
getinformation about what<br />> reloptions have been set.<br />><br /><br />Maybe into "information_schema"
??<br/><br />Regards,<br /><br />--<br />Fabrízio de Royes Mello<br />Consultoria/Coaching PostgreSQL<br />>>
Timbira:<a href="http://www.timbira.com.br">http://www.timbira.com.br</a><br />>> Blog: <a
href="http://fabriziomello.github.io">http://fabriziomello.github.io</a><br/>>> Linkedin: <a
href="http://br.linkedin.com/in/fabriziomello">http://br.linkedin.com/in/fabriziomello</a><br/>>> Twitter: <a
href="http://twitter.com/fabriziomello">http://twitter.com/fabriziomello</a><br/>>> Github: <a
href="http://github.com/fabriziomello">http://github.com/fabriziomello</a></div>