On 1/12/2005 7:40 AM, David Parker wrote:

> Oh, if I changed my oid fields to bytea, slony could replicate them? 
> 
> I have to look into whether bytea would work for our app, of course - I
> haven't used it before, but having those puppies slony-replicated would
> be a huge help to me....

Not only that they can be Slony-I replicated then. Large Objects can be 
orphaned and there is no ON DELETE CASCADE for them.


Jan

> 
> Thanks.
> 
> - DAP 
> 
>>-----Original Message-----
>>From: slony1-general-bounces at gborg.postgresql.org 
>>[mailto:slony1-general-bounces at gborg.postgresql.org] On Behalf 
>>Of Andrew Sullivan
>>Sent: Wednesday, January 12, 2005 6:38 AM
>>To: slony1-general at gborg.postgresql.org
>>Subject: Re: [Slony1-general] current slony1 limitations
>>
>>On Tue, Jan 11, 2005 at 08:17:07PM -0800, Nick Pavlica wrote:
>>> Are there reliable methods to work around these limitations?
>>
>>Sort of.  BLOBs, no, although you could use bytea.  And you 
>>can propogate schema changes via slonik scripts.
>>
>>There are rumours that MySQL's replication occasionally loses 
>>data silently.  I haven't tested it.
>>
>>A
>>
>>--
>>Andrew Sullivan  | ajs at crankycanuck.ca
>>In the future this spectacle of the middle classes shocking 
>>the avant- garde will probably become the textbook definition 
>>of Postmodernism. 
>>                --Brad Holland
>>_______________________________________________
>>Slony1-general mailing list
>>Slony1-general at gborg.postgresql.org
>>http://gborg.postgresql.org/mailman/listinfo/slony1-general
>>
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at gborg.postgresql.org
> http://gborg.postgresql.org/mailman/listinfo/slony1-general


-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck at Yahoo.com #