From: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Default to TIMESTAMP WITH TIME ZONE? |
Date: | 2021-08-13 00:16:09 |
Message-ID: | CAMsGm5c3UPRhP0CpMEJXtg0rzFec35TG=wV0+L04p-9VBwks_g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
An idea just occurred to me: a systematic way to provide this feature might
be to support aliases for objects. So I could declare an alternate name for
an object, something like:
CREATE ALIAS timestamp FOR TYPE timestamptz;
Which would mean that [current schema].timestamp would now be an alternate
name for the built-in timestamptz object. There are other situations in
which being able to define aliases would be handy, including schema
migrations and probably other compatibility scenarios.
Of course I'm aware that this idea itself would need a lot of discussion
and I'm not volunteering to implement it right now, but it might be a
workable approach if aliases ever become a feature.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-08-13 00:29:09 | Re: Worth using personality(ADDR_NO_RANDOMIZE) for EXEC_BACKEND on linux? |
Previous Message | Jacob Champion | 2021-08-13 00:08:16 | Re: [PATCH] test/ssl: rework the sslfiles Makefile target |