| From: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Brendan Jurd <direvus(at)gmail(dot)com>, "pgsql-hackers(at)postgreSQL(dot)org" <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: About the CREATE TABLE LIKE indexes vs constraints issue |
| Date: | 2009-12-24 14:21:11 |
| Message-ID: | 88FF7F53-2AFA-4958-A60C-B06A5308A891@hi-media.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi, sorry for posting style,
--
dim
Le 23 déc. 2009 à 23:58, Jeff Davis <pgsql(at)j-davis(dot)com> a écrit :
> Honestly, I've never used LIKE in a table definition aside from one-
> off
> design experiments. For that kind of thing, what I want is to just get
> everything (except perhaps FKs if the above situation applies), and I
> adjust it from there. Are there people out there who use LIKE in their
> production schema files?
I do use LIKE in scripts for adding providers of federated data. In
some cases you want to INHERIT, in some other you want to move
incoming data to another set of tables.
Regards,
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2009-12-24 15:47:34 | Re: Backup history file should be replicated in Streaming Replication? |
| Previous Message | Simon Riggs | 2009-12-24 09:58:20 | Re: Streaming Rep - 2-phase backups and reducing time to full replication |