From: | Rémi Cura <remi(dot)cura(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | Steven Erickson <Steven(dot)Erickson(at)telventdtn(dot)com>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: partitoning expert : Partitonning with specialization of one column type |
Date: | 2015-04-01 15:09:21 |
Message-ID: | CAJvUf_uHLdJD=Ztqr9BmU8jDxq8bFTL1DFkmFmKsE+axJjMD3Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Okay,
thanks for the answer.
I take it that it is "do it differently then".
I might have an idea but it is not working yet, so I'll post another
message.
Thanks dear co-list user ^^
Cheers,
Rémi-C
2015-04-01 16:56 GMT+02:00 David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>:
> On Wed, Apr 1, 2015 at 7:26 AM, Rémi Cura <remi(dot)cura(at)gmail(dot)com> wrote:
>
>> pcpatch(n) are specialization of pcpatch type.
>>
>
> While this may be true PostgreSQL doesn't understand "specialization" of
> data types. If you cannot do as Steven suggested you do not get to
> leverage inheritance directly and will need to devise your own work-arounds
> for the capabilities that you require.
>
> I'm somewhat surprised that what you describe works at all - mainly given
> that functions do not allow typemod specifications to pass through the
> function invocation...but alas I'm not all that familiar with PostGIS and
> whatever is being done does indeed seem to be working...
>
> David J.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2015-04-01 15:09:23 | Re: stack builder |
Previous Message | Ramesh T | 2015-04-01 14:59:19 | Re: stack builder |