On Tuesday 04 April 2006 13:15, Darcy Buskermolen wrote:
> On Tuesday 04 April 2006 13:03, Jan Wieck wrote:
> > On 4/4/2006 2:49 PM, Glen Eustace wrote:
> > > Table 9 still exists in _gz_admin.sl_table;
> > >
> > >       9 |    9527801 | domain_registry_history | public      |       3
> > > | domain_registry_history_pkey | t           | Domain Registry
> > >
> > > and still exists for real in the database.
> >
> > This is odd. Can it be that the table has been dropped and recreated,
> > and thereby it's OID changed? If the tables OID in pg_class is different
> > from the tab_reloid in sl_table (9527801), that would explain the error.
> >
> > There is an (undocumented?) slonik command
> >
> >    REPAIR CONFIG
> >      (set id = <int>[, event node = <int>] [, execute only on = <int>]);
> >
> > Which should take care of this problem.
> >
> > Why is it undocumented? Chris?
>
> I'm sure I submitted documentation on this.  Let me check my local repo

Ok good I'm not loosing my mind I did infact commit it,  see rev 1.14 of 
doc/howto/slonik_commands.html  By the looks of it this was happening at 
about the same time as Chris was sgmlifying the docs.


>
> > Jan
> >
> > > It has the following rules and indices;
> > > Indexes:
> > >     "domain_registry_history_pkey" PRIMARY KEY, btree ("domain",
> > > tstamp) "domain_registry_history_idx1" btree (client, "domain", tstamp)
> > > Triggers:
> > >     _gz_admin_logtrigger_9 AFTER INSERT OR DELETE OR UPDATE ON
> > > domain_registry_history FOR EACH ROW EXECUTE PROCEDURE
> > > _gz_admin.logtrigger('_gz_admin', '9', 'vkkvvvvvvvvvvvvv')
> > >
> > > It also has a view which includes update rules.
> > >
> > > Where to next ?

-- 
Darcy Buskermolen
Wavefire Technologies Corp.

http://www.wavefire.com
ph: 250.717.0200
fx: 250.763.1759