On Monday 24 July 2006 09:05, Csaba Nagy wrote:
> On Mon, 2006-07-24 at 17:59, cbbrowne at ca.afilias.info wrote:
> > > Are
> > > the problems related to the fact that there's  no way to catch blob
> > > updates using triggers ?
> >
> > Head.  Nail.  Struck on...
> >
> > Yes, that is exactly the problem with BLOB support.  There isn't a way to
> > detect updates to BLOB objects via triggers.
>
> OK... but the partial support with explicitly stating you shouldn't
> update blobs would work out ? For us that would be sufficient, we don't
> update blobs. We might _replace_ a blob, but never update the content
> directly... I guess that would be tractable, right ?
>
> If you hint me it's not very hard to hack that in I could try to do it
> locally and experiment a bit...

The problem is there is no way to catch the lo_import(). And if you could, I'm 
not sure you could preserve the oid of the LO between nodes. All of this puts 
you down the path of replicating LO's at the application level I'd think.

>
> Thanks,
> Csaba.
>
>
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at gborg.postgresql.org
> http://gborg.postgresql.org/mailman/listinfo/slony1-general

-- 
Darcy Buskermolen
Wavefire Technologies Corp.

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