> Rod, can you lay out some psdueo code / logic involved in the process? I'm
> guessing you lock the entry in pg_class, you up dependent objects, lock them,
> update them all... is there more to it?
It was one an offline database at the time with only a single user -- so
locking wasn't a concer
On Sunday 15 February 2004 07:53, Rod Taylor wrote:
> On Sun, 2004-02-15 at 01:34, Neil Conway wrote:
> > [EMAIL PROTECTED] writes:
> > > The capability to move objects to other schemas would be quite
> > > useful.
> >
> > I agree. It's not utterly-trivial to implement (for one thing, you
> > need
Rod Taylor wrote:
-- Start of PGP signed section.
> On Sun, 2004-02-15 at 01:34, Neil Conway wrote:
> > [EMAIL PROTECTED] writes:
> > > The capability to move objects to other schemas would be quite
> > > useful.
> >
> > I agree. It's not utterly-trivial to implement (for one thing, you
> > need t
On Sun, 2004-02-15 at 01:34, Neil Conway wrote:
> [EMAIL PROTECTED] writes:
> > The capability to move objects to other schemas would be quite
> > useful.
>
> I agree. It's not utterly-trivial to implement (for one thing, you
> need to move any dependant objects like indexes to the new schema),
>
[EMAIL PROTECTED] writes:
> The capability to move objects to other schemas would be quite
> useful.
I agree. It's not utterly-trivial to implement (for one thing, you
need to move any dependant objects like indexes to the new schema),
but some form of this functionality would be a useful thing to
Hello!
The following SQL works:
ALTER TABLE a.foo RENAME TO bar;
But the following doesn't:
ALTER TABLE a.foo RENAME TO b.bar;
The capability to move objects to other schemas
would be quite useful.
Apparently, everything works OK if you change
pg_class.relnamespace with UPDATE, but this is
no
