| From: | Craig Ringer <craig(dot)ringer(at)2ndquadrant(dot)com> |
|---|---|
| To: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WG: Packages: Again |
| Date: | 2017-01-13 14:11:46 |
| Message-ID: | CAMsr+YEUEbT4VqQutc5R=gGmTu0ADHAXBmvdZq6-LXYfk4KuOg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 13 Jan. 2017 19:16, "Thomas Kellerer" <
Which is a bit cumbersome given Oracle's limit on 30 characters for
identifiers - but it still increases maintainability. And one of the
advantages given for packages was the increase in namespace availability
which is much easier with Postgres anyway.
I was wondering where the namespace thing came from. Sure,
packagename_funcname I'd cumbersome but it's not exactly hard and we've
been doing it in C since forever.
I'd assumed it was an issue in the opposite direction. PG identifiers being
too short. But it sounds like instead it's people not realising they can do
this.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Moser | 2017-01-13 14:22:14 | Re: [PROPOSAL] Temporal query processing with range types |
| Previous Message | Craig Ringer | 2017-01-13 14:08:29 | Re: BUG: pg_stat_statements query normalization issues with combined queries |