Re: [GENERAL] Column Tetris Automatisation

2017-01-15 Thread Adam Brusselback
I for one would love having something like this available. I also know i've seen discussed in the past, divorcing the physical column order from the logical column order, which seems like it'd be useful here as well to not break the workflow of those who do use ordinal positions for columns.

Re: [GENERAL] Column Tetris Automatisation

2017-01-15 Thread Mike Sofen
|From: Nicolas Paris |Hello, |In postgresl order of columns does have an non negligeable impact on table |size[1]. |Table are in many cases dynamic, and new fields can appear in the database life. |I suspect re-ordering columns based on types would be an automatisable task | |Moreover, most client

Re: [GENERAL] Column Tetris Automatisation

2017-01-15 Thread Pavel Stehule
Hi 2017-01-15 10:58 GMT+01:00 Nicolas Paris : > Hello, > > In postgresl order of columns does have an non negligeable impact on table > size[1]. > Table are in many cases dynamic, and new fields can appear in the database > life. > I suspect re-ordering columns based on types would be an automati

[GENERAL] Column Tetris Automatisation

2017-01-15 Thread Nicolas Paris
Hello, In postgresl order of columns does have an non negligeable impact on table size[1]. Table are in many cases dynamic, and new fields can appear in the database life. I suspect re-ordering columns based on types would be an automatisable task would be feaseable such: ``` reorderTableWithTe