Tue May 30 08:01:28 PDT 2006
- Previous message: [Slony1-general] slony-I replication tables with multiple primary keys
- Next message: [Slony1-general] slony-I replication tables with multiple primary keys
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 5/30/2006 7:14 AM, Matthew Whittaker-Williams wrote: > On Tuesday 30 May 2006 13:11, Matthew Whittaker-Williams wrote: >> Hi, >> >> I was wondering if it is possible to define multiple primary keys in the >> set add table function. >> >> Like so: >> >> set add table ( set id = 1, origin = 1, id = 54, full qualified name >> = 'public,foo_map, key = 'foo1,foo2', comment = 'Table foo_map'); > > Whoops.. > > Should be this: > > set add table ( set id = 1, origin = 1, id = 54, full qualified name > = 'public,foo_map', key = 'foo1,foo2', comment = 'Table foo_map'); Since the key used for Slony-I must be unique and not-null, specifying multiple keys is totally pointless. Are you eventually mixing up multi-column keys with multiple keys? You don't specify the column names but rather the index name in the SET ADD TABLE command. If that happens to be a unique index over multiple not-null columns, no problem. Jan > > Matthew -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck at Yahoo.com #
- Previous message: [Slony1-general] slony-I replication tables with multiple primary keys
- Next message: [Slony1-general] slony-I replication tables with multiple primary keys
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list