I just removed the operator column from the sql query which produced the error.
It seemed to work for the moment.
But I will add the column as soon as the indexing took place.
Thanks,
Michael
-Ursprüngliche Nachricht-
Von: twai...@gmail.com [mailto:twai...@gmail.com] Im Auftrag von Brian Quinion
Gesendet: Dienstag, 12. Oktober 2010 16:37
An: Lück, Michael
Cc: dev@openstreetmap.org
Betreff: Re: [OSM-dev] Postgres Error with gazetteer database for nominatim
Nothing you missed - something I missed.
I have once again (I really need to stop doing this!) committed half a
set of changes.
To get you back working just do:
alter table word add column operator text;
null values default to the current behaviour.
--
Brian
On 11 October 2010 15:22, Lück, Michael
michael.lu...@bonk-consulting.de wrote:
Hi all,
we set up our own nominatim server as described on
http://wiki.openstreetmap.org/wiki/Nominatim/Installation .
We took latest revision of osm2pgsql from the svn
http://svn.openstreetmap.org/applications/utils/export/osm2pgsql.
Everything seems to work until we try to search for an city or something.
Then we get the following error:
nativecode=FEHLER: Spalte »operator« existiert nicht at character 71
In Englisch:
nativecode=ERROR: Column operator doesn't exist at
character 71
The SQL Statement fired against the database is
select word_id,word_token, word, class, type, location,
country_code, operator from word where word_token in (' ilmenau','ilmenau','
germany','germany');
I had a look at the table world and it really does not contain an column
called operator.
Did we miss something?
Regards,
Michael
___
dev mailing list
dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/dev
___
dev mailing list
dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/dev