Re: updated WIP: arrays of composites
| От | Gregory Stark | 
|---|---|
| Тема | Re: updated WIP: arrays of composites | 
| Дата | |
| Msg-id | 878xbv89xv.fsf@oxford.xeocode.com обсуждение исходный текст  | 
		
| Ответ на | Re: updated WIP: arrays of composites (Tom Lane <tgl@sss.pgh.pa.us>) | 
| Ответы | 
                	
            		Re: updated WIP: arrays of composites
            		
            		 | 
		
| Список | pgsql-patches | 
"Tom Lane" <tgl@sss.pgh.pa.us> writes: > * I'm a bit concerned about dump order. If a user wants to create > types named "foo" and "_foo", he can, but it will only work if he > makes "_foo" first --- else the derived type for foo is in the way. > Since pg_dump has no clue about that constraint, it might easily > dump "foo" first leading to an unrestorable dump. The most usable > solution would be to auto-rename previously created array types, > but I dunno how implementable that would be. BTW, why exactly do we need array types to have names at all? The only user-visible way to refer to these types is always by foo[] isn't it? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com
В списке pgsql-patches по дате отправления: