Wed Nov 29 07:03:43 PST 2006
- Previous message: [Slony1-general] Porting slony to allow oracle to be master (no slave required)
- Next message: [Slony1-general] Porting slony to allow oracle to be master (no slave required)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, 2006-11-29 at 15:50, Shoaib Mir wrote: > It should be able to replicate to stock PostgreSQL as well but then > you will be having problems when replicating Oracle like data types to > PostgreSQL as EnterpriseDB is provided Oracle compatible features. Hmm, that's true, but that could be handled if the corresponding fields are convertible to each other. I'm not sure how slony is working, but if it would allow the data to be transmitted in it's text format and not binary, the data conversion could work just fine. Our corresponding fields in Oracle/postgres are mostly compatible, problems come in for boolean types mostly, and that can be solved by creating some implicit casts which solve the issue. So it all boils down on how the data is transferred, text or binary, and strictly typed or not... Cheers, Csaba.
- Previous message: [Slony1-general] Porting slony to allow oracle to be master (no slave required)
- Next message: [Slony1-general] Porting slony to allow oracle to be master (no slave required)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list