Thread: Ticket 133: New attoptions column in pg_attribute
Hi, This new column replaces the attdistinct one. So I add to undo my previous patch (see http://code.pgadmin.org/trac/ticket/95) and work on the new syntax. AFAICT, it works well on Linux. The behaviour should be the same on other platforms. Comments? -- Guillaume. http://www.postgresqlfr.org http://dalibo.com
Attachment
Le 26/01/2010 23:09, Guillaume Lelarge a écrit : > [...] > This new column replaces the attdistinct one. So I add to undo my > previous patch (see http://code.pgadmin.org/trac/ticket/95) and work on > the new syntax. > > AFAICT, it works well on Linux. The behaviour should be the same on > other platforms. > > Comments? > I should probably explain more what I did. I added a Variables tab (copied/pasted from the tablespace dialog). It only handles two variables, which are not in pg_settings. So I get rid of the checkbox (they both are numeric values) and drop the array of struct (type, min value, max value) which is not needed here (at least now). I can undo my deletes if required. -- Guillaume. http://www.postgresqlfr.org http://dalibo.com
Le 26/01/2010 23:14, Guillaume Lelarge a écrit : > Le 26/01/2010 23:09, Guillaume Lelarge a écrit : >> [...] >> This new column replaces the attdistinct one. So I add to undo my >> previous patch (see http://code.pgadmin.org/trac/ticket/95) and work on >> the new syntax. >> >> AFAICT, it works well on Linux. The behaviour should be the same on >> other platforms. >> >> Comments? >> > > I should probably explain more what I did. I added a Variables tab > (copied/pasted from the tablespace dialog). It only handles two > variables, which are not in pg_settings. So I get rid of the checkbox > (they both are numeric values) and drop the array of struct (type, min > value, max value) which is not needed here (at least now). I can undo my > deletes if required. > Commited. -- Guillaume. http://www.postgresqlfr.org http://dalibo.com