[Mapbender-dev] PostgreSQL 8.4 problems

[Thomas Baschetti]

Hm,

perhaps this is 'old' syntax (PG 7.X) and we can use
alter table abc disable trigger all; ?

And is this really needed at all in newer postgresql-Versions?

Will test it tomorrow, too.

Bye
Thomas

Michael Schulz schrieb:
> Hi Thomas,
>
> this is needed for the import of the wms, and layer data i think,
> because these tables habe prim keys and constraints to foreign keys.
> this constraint checking is basically disabled before inserting the
> data and the again activated.
>
> Have a look in the wiki for the howto compile a mapbender release ...
> or similar.
>
> I think so too, that this should be fixed for 2.6. I can also have a
> look at it tomorrow.
>
> Cheers, Michael
>
>
> 2009/8/13 Thomas Baschetti <info at thomas-baschetti.de>:
>   
>> Hi,
>>
>> apperently PostgreSQL 8.4 can't be used to create a new Mapbender-database,
>> see http://trac.osgeo.org/mapbender/ticket/508
>> for details.
>>
>> My Question: How is this dump created? If i use pgadmin3 or pg_dump
>> directly, there is no such command as "update pg_catalog.pg_class ...".
>>
>> Why is this needed?
>>
>> I think we should fix this in 2.6.
>> Bye
>> Thomas
>>
>>     

-- 

Thomas Baschetti - Systemanalyse Geographische Informationssysteme
Hakenstraße 8D
49074 Osnabrück

Tel: 0541 25 91 90 | mobil 01577 189 25 91
E-Mail: info at thomas-baschetti.de
www.thomas-baschetti.de
Ust-IdNr.: DE264355072