it's because it's looking for public.public.euro_rates.   I've been 
bitten by this before too.
if you supply an invalid table name, you get the "has no primary key" 
message, not a "table
foo doesn't exist" message

--brian

On Feb 3, 2005, at 7:34 AM, Hannu Krosing wrote:

> It seems that if primary key is on fields of type (date, text)
> then slony cant find it:
>
> postgres at db1:~/replicator/accdb2$ ./01_add_table_to_new_set2.sh
> <stdin>:50: PGRES_FATAL_ERROR select
> "_accountdb_cluster".determineIdxnameUnique('public.public.euro_rates',
> NULL);  - ERROR:  Slony-I: table public.public.euro_rates has no 
> primary
> key
>
> postgres at db1:~/replicator/accdb2$ psql accountdb
> Welcome to psql 7.4.5, the PostgreSQL interactive terminal.
>
> accountdb=# \d euro_rates
>         Table "public.euro_rates"
>    Column    |      Type      | Modifiers
> -------------+----------------+-----------
>  id_date     | date           | not null
>  id_currency | text           | not null
>  rate        | numeric(20,10) |
> Indexes:
>     "euro_rates_pkey" primary key, btree (id_date, id_currency)
>
> Is it a known problem or is something wrong with my setup ?
>
> slony version is plain 1.0.5
>
> -------------
> Hannu
>
>
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at gborg.postgresql.org
> http://gborg.postgresql.org/mailman/listinfo/slony1-general
>
>
--------------------------------------------
MobyGames
http://www.mobygames.com
The world's largest and most comprehensive?
gaming database project