[postgis-devel] [PostGIS] #1288: Update Best practices

[PostGIS]

#1288: Update Best practices
---------------------------+------------------------------------------------
 Reporter:  robe           |       Owner:  robe         
     Type:  task           |      Status:  new          
 Priority:  medium         |   Milestone:  PostGIS 2.0.0
Component:  documentation  |     Version:  trunk        
 Keywords:                 |  
---------------------------+------------------------------------------------
Description changed by robe:

Old description:

> A lot of the best practices have changed with 2.0 and sadly I haven't had
> time yet to go thru the documentation we have to correct.
>
> Glaring issues:
> 1) How to create geometry tables.
> 2) As strk pointed out -- how to define indexes on tables
> including example of an nd index.
> 3) How to install/upgrade.  This will change for 9.1, and I haven't put
> in the new extension install approach yet since I don't have an upgrade
> extension script finalized yet so the old way is still the best way for
> 9.1 (while 2.0 is in flux).
> 4) I'm sure we've still got some deprecated function calls in the docs
> too.
>
> Anyrate if people want to help out scanning the docs for things that no
> longer make sense in 2.0, and just tack it to this ticket, that would be
> helpful.  Patches welcome.

New description:

 A lot of the best practices have changed with 2.0 and sadly I haven't had
 time yet to go thru the documentation we have to correct.


 Glaring issues:

 1) How to create geometry tables.

 2) As strk pointed out -- how to define indexes on tables
 including example of an nd index.

 3) How to install/upgrade.  This will change for 9.1, and I haven't put in
 the new extension install approach yet since I don't have an upgrade
 extension script finalized yet so the old way is still the best way for
 9.1 (while 2.0 is in flux).

 4) I'm sure we've still got some deprecated function calls in the docs
 too.

 Anyrate if people want to help out scanning the docs for things that no
 longer make sense in 2.0, and just tack it to this ticket, that would be
 helpful.  Patches welcome.

--

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1288#comment:1>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.