William Bug wrote:
>
>
> I'm not certain I understand what you mean here? Are you recommending
> all application layer interaction with tables using INHERIT should be
> done via a VIEW intermediary? If so, wouldn't the VIEW (built from a
> "SELECT ... ONLY...") then be as dependent on the f
Once again, many many thanks Jeff for taking the time to think
through these issues and provide your well-informed comments & opinions!
On Aug 10, 2005, at 4:09 PM, Jeff Davis wrote:
William Bug wrote:
As you say, both LIKE & INHERIT are a bit anemic and unnecessary,
since
what they provi
William Bug wrote:
> As you say, both LIKE & INHERIT are a bit anemic and unnecessary, since
> what they provide can be implemented via VIEWs and RULEs/ TRIGGERs. I'd
I'd like to point out that INHERITS is unique, although I'm not sure all
of the exact differences. The main difference that I see
William Bug wrote:
> Hi All,
>
> Sorry to bring up the topic of PostgreSQL inheritance again, but after
> going through the archives and Google results, I still don't have a
> clear sense of whether my plan to implement a schema I'm working on is
> the preferred way to go.
>
> First, I'd like
Hi All,
Sorry to bring up the topic of PostgreSQL inheritance again, but
after going through the archives and Google results, I still don't
have a clear sense of whether my plan to implement a schema I'm
working on is the preferred way to go.
First, I'd like to find out if the way I'm thi
Dear pgsql-general moderators,
I sent this post out over the weekend.
Is there a reason why it is not getting posted to the list?
Many thanks for your assistance. I really need some advice on this
issue from people with experience using both inheritance mechanisms
in PostgreSQL.
Cheers,
