-Original Message-
From: Jim C. Nasby [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 19, 2005 5:56 PM
To: Christopher Browne
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] argtype_inherit() is dead code
[...]
On Sun, Apr 17, 2005 at 07:01:41PM -0400, Christopher Browne
On Sun, Apr 17, 2005 at 07:01:41PM -0400, Christopher Browne wrote:
The world rejoiced as [EMAIL PROTECTED] (Jim C. Nasby) wrote:
On Sun, Apr 17, 2005 at 06:56:01AM -0700, Joshua D. Drake wrote:
Is it really an important area to improve, or are there other
priorities? I know some people
, 2005 6:56 AM
To: Alvaro Herrera
Cc: Tom Lane; elein; pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] argtype_inherit() is dead code
Is it really an important area to improve, or are there other
priorities? I know some people wished we had better support for
inheritance, but how strong
The world rejoiced as [EMAIL PROTECTED] (Jim C. Nasby) wrote:
On Sun, Apr 17, 2005 at 06:56:01AM -0700, Joshua D. Drake wrote:
Is it really an important area to improve, or are there other
priorities? I know some people wished we had better support for
inheritance, but how strong is that
Alvaro Herrera wrote:
On Sun, Apr 17, 2005 at 06:56:01AM -0700, Joshua D. Drake wrote:
From a people who call me perspective. I am never asked about
inheritance. Most of the people don't even know it is there.
The requests I get are:
Just wondering, does anybody asks you about the
Alvaro Herrera wrote:
On Sun, Apr 17, 2005 at 06:56:01AM -0700, Joshua D. Drake wrote:
From a people who call me perspective. I am never asked about
inheritance. Most of the people don't even know it is there.
The requests I get are:
Just wondering, does anybody asks you about the excessive
Is it really an important area to improve, or are there other
priorities? I know some people wished we had better support for
inheritance, but how strong is that wish?
Hello,
From a people who call me perspective. I am never asked about
inheritance. Most of the people don't even know it is
On Sun, Apr 17, 2005 at 06:56:01AM -0700, Joshua D. Drake wrote:
From a people who call me perspective. I am never asked about
inheritance. Most of the people don't even know it is there.
The requests I get are:
Just wondering, does anybody asks you about the excessive locking (and
As the voice of someone who has a lot of experience with
some of the original inheritance, I would prefer to
have the select foo(t.*) from grandkid work for
completeness.
However, erroring out as ambiguous is not unreasonable
since we have to cast the hell out of everything usually.
I would
On Sun, Apr 17, 2005 at 06:56:01AM -0700, Joshua D. Drake wrote:
Is it really an important area to improve, or are there other
priorities? I know some people wished we had better support for
inheritance, but how strong is that wish?
FWIW, I think people might be more likely to use the OO
On Sun, 2005-04-17 at 14:04 -0400, Alvaro Herrera wrote:
On Sun, Apr 17, 2005 at 06:56:01AM -0700, Joshua D. Drake wrote:
From a people who call me perspective. I am never asked about
inheritance. Most of the people don't even know it is there.
The requests I get are:
Just wondering,
On Sun, 2005-04-17 at 19:54 -0400, Robert Treat wrote:
On Sunday 17 April 2005 19:30, Rod Taylor wrote:
On Sun, 2005-04-17 at 14:04 -0400, Alvaro Herrera wrote:
On Sun, Apr 17, 2005 at 06:56:01AM -0700, Joshua D. Drake wrote:
From a people who call me perspective. I am never asked about
On Sunday 17 April 2005 19:30, Rod Taylor wrote:
On Sun, 2005-04-17 at 14:04 -0400, Alvaro Herrera wrote:
On Sun, Apr 17, 2005 at 06:56:01AM -0700, Joshua D. Drake wrote:
From a people who call me perspective. I am never asked about
inheritance. Most of the people don't even know it is
From a people who call me perspective. I am never asked about
inheritance. Most of the people don't even know it is there.
The requests I get are:
Just wondering, does anybody asks you about the excessive locking (and
deadlocking) on foreign keys? The business about being able to drop
users and
Are you saying that the code was supposed unflatten the
arguments of a function into a possible composite type taking into
consideration the possible inheritance information of the
composite type?
elein
On Fri, Apr 15, 2005 at 08:04:36PM -0400, Tom Lane wrote:
In parse_func.c there are routines
[EMAIL PROTECTED] (elein) writes:
Are you saying that the code was supposed unflatten the
arguments of a function into a possible composite type taking into
consideration the possible inheritance information of the
composite type?
No, it didn't do that. AFAICT the case it was supposed to
On Sat, Apr 16, 2005 at 03:39:55PM -0400, Tom Lane wrote:
Digging in the CVS history, it appears that I may have broken it here:
http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_coerce.c.diff?r1=2.35;r2=2.36;f=h
It's quite possible that it failed even before that
Alvaro Herrera [EMAIL PROTECTED] writes:
Given the limitations of table inheritance, it doesn't surprise me that
nobody really uses it to implement object-oriented programs.
True.
Is it really an important area to improve, or are there other priorities?
There are certainly higher priorities,
In parse_func.c there are routines argtype_inherit() and
gen_cross_product() that date from Berkeley days. The comments
explain their reason for existence thus:
* This function is used to handle resolution of function calls when
* there is no match to the given argument types, but there
19 matches
Mail list logo
