On Tue, Apr 12, 2005 at 01:04:20PM -0400, Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
What about the simple one of having a bool pg_cast.castissystem
column, or something similar?
This one is sounding pretty good to me, though I'd be inclined to call
it castisbuiltin or some
Tom Lane wrote:
Also, it would ideally be possible to deliberately create a new cast
that pg_dump would ignore --- you can do this for other object kinds
by creating them in the pg_catalog schema.
It's a little bit odd to think of casts as belonging to schemas,
since they don't have names in the
On Tue, Apr 12, 2005 at 08:39:09AM +0200, Michael Paesold wrote:
Tom Lane wrote:
The other possible solution that comes to mind is to invent the notion
that a cast has a specific owner (which arguably it should have anyway)
and then say that system casts are those whose owner is the original
Alvaro Herrera wrote:
On Tue, Apr 12, 2005 at 08:39:09AM +0200, Michael Paesold wrote:
Tom Lane wrote:
The other possible solution that comes to mind is to invent the notion
that a cast has a specific owner (which arguably it should have anyway)
and then say that system casts are those whose
Alvaro Herrera [EMAIL PROTECTED] writes:
But yes, schema-qualifying casts seems weird:
'123'::someschema.user_type
Is that even accepted by the grammar?
Yes, but it'd be taken as a qualification on the type name not the cast
per se. Offhand I'm not sure where we could even put a schema name
On Tue, Apr 12, 2005 at 06:38:41PM +0200, Michael Paesold wrote:
Alvaro Herrera wrote:
On Tue, Apr 12, 2005 at 08:39:09AM +0200, Michael Paesold wrote:
Tom Lane wrote:
The other possible solution that comes to mind is to invent the
notion that a cast has a specific owner (which arguably
On 2005-04-12, Alvaro Herrera [EMAIL PROTECTED] wrote:
Well perhaps there is an even better solution?
What about the simple one of having a bool pg_cast.castissystem
column, or something similar?
Checking the OID might be sufficient if it were possible to make the OID
counter restart at some
Alvaro Herrera [EMAIL PROTECTED] writes:
What about the simple one of having a bool pg_cast.castissystem
column, or something similar?
This one is sounding pretty good to me, though I'd be inclined to call
it castisbuiltin or some such.
regards, tom lane
On Tue, Apr 12, 2005 at 05:04:03PM -, Andrew - Supernews wrote:
On 2005-04-12, Alvaro Herrera [EMAIL PROTECTED] wrote:
Well perhaps there is an even better solution?
What about the simple one of having a bool pg_cast.castissystem
column, or something similar?
Checking the OID might
Alvaro Herrera [EMAIL PROTECTED] writes:
On Tue, Apr 12, 2005 at 05:04:03PM -, Andrew - Supernews wrote:
Checking the OID might be sufficient if it were possible to make the OID
counter restart at some value known to be greater than any datlastsysoid,
rather than restarting at
On Sunday 10 April 2005 19:10, Jim C. Nasby wrote:
In working on the newsysviews project we've discovered that there's no
definitive way to determine if a cast is a system cast (system as in
part of postgresql/created by createdb) or not. What pg_dump does (and
what we're doing now for lack of
On 2005-04-12, Robert Treat [EMAIL PROTECTED] wrote:
One potential ugly way to do it would be to use the magical last system oid
as a differentiator between those created by pg and those created by the
user. It would be different for every version so that might be a problem.
That is what
Andrew - Supernews [EMAIL PROTECTED] writes:
On 2005-04-12, Robert Treat [EMAIL PROTECTED] wrote:
One potential ugly way to do it would be to use the magical last system
oid
That is what pg_dump does when talking to pre-7.2 databases. But it isn't
entirely reliable because oid wrap can
In working on the newsysviews project we've discovered that there's no
definitive way to determine if a cast is a system cast (system as in
part of postgresql/created by createdb) or not. What pg_dump does (and
what we're doing now for lack of a better solution) is any cast that
doesn't involve a
14 matches
Mail list logo
