Sun Feb 12 11:06:31 PST 2006
- Previous message: [Slony1-general] Problem between Slony 1.1.5 and PostgreSQL 8.1.2 ...
- Next message: [Slony1-general] what constitutes a suitable 'primary key'?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Apparently a UNIQUE index doesn't?
=# \d bit1
Table "public.bit1"
Column | Type | Modifiers
---------------+-----------------------------+---------------
instance_id | integer | not null
instance_name | character varying(500) | not null
created_on | timestamp without time zone | default now()
code | text |
md5sum | text |
status | text |
activated_on | text |
esdnet_uuid | text |
license | text |
account_uuid | text |
Indexes:
"bit1_instance_id_key" UNIQUE, btree (instance_id)
"bit1lin_idx" btree (lower(instance_name::text))
Gets reported by slony has having no primary key:
ERROR: Slony-I: table "public"."bit1" has no primary key
So, just to clarify before I do it, all tables that have 'just a UNIQUE
key', I'll still have to do 'ALTER TABLE <table> ADD PRIMARY KEY ( field
);' to so that Slony likes them?
- Previous message: [Slony1-general] Problem between Slony 1.1.5 and PostgreSQL 8.1.2 ...
- Next message: [Slony1-general] what constitutes a suitable 'primary key'?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list