One of the cooler things with the geo module is the potential ability to integrate drupal with existing GIS repositories, and to use geo data stored in drupal as a data layer in desktop GIS programs (such as Quantum GIS: www.qgis.org). Suddenly Drupal with postGIS and geo becomes a competitor to ArcIMS at al with the ability to act as the repository of an organization's GIS data.

In order to get desktop GIS programs such as qgis to read geo tables, "WITH OIDS" must be used to create the tables.

Comments

allie micka’s picture

allie micka
she/her
commented
Status: Active » Postponed (maintainer needs more info)

Hi phayes,

I'm not entirely sure how much of this is in my bailiwick. I have tried to rely on the schema API as much as possible. In recent versions of Geo_field, I have figured out a way to outsource table/field definition entirely to CCK. I am defining an array of fields that should be in a table, and CCK is creating that table.

In cases where you go from single- to multi-value, or when you add a field to a new content type, the original table is dropped and recreated by CCK. Handy, but tricky to interfere with!

Long story short, I don't know that I can come along and affect table creation calls. According to my vast knowledge of the "WITH OIDS" clause (AKA what I read on http://www.postgresql.org/docs/8.2/static/sql-createtable.html ), it seems that you can control this with default_with_oids. Is it acceptable to document this requirement and call it good? Can you confirm/deny that this is even effective?

Thanks!

phayes’s picture

phayes commented
Status: Postponed (maintainer needs more info) » Closed (won't fix)

That's fine. Thanks for looking into this. Indeed running postgres with default_with_oids should work. I might open this again when D7 comes out with the new fields API.