[GRASS-dev] [GRASS GIS] #2258: t.create creates DB always in the PERMANENT

GRASS GIS trac at osgeo.org
Fri Jun 6 15:42:56 PDT 2014


#2258: t.create creates DB always in the PERMANENT
-------------------------+--------------------------------------------------
 Reporter:  martinl      |       Owner:  grass-dev@…              
     Type:  defect       |      Status:  new                      
 Priority:  normal       |   Milestone:  7.0.0                    
Component:  Temporal     |     Version:  svn-releasebranch70      
 Keywords:  t.register   |    Platform:  Unspecified              
      Cpu:  Unspecified  |  
-------------------------+--------------------------------------------------

Comment(by huhabla):

 Replying to [comment:7 neteler]:
 > Replying to [comment:5 huhabla]:
 > > Replying to [comment:4 glynn]:
 > > > Replying to [comment:3 huhabla]:
 > > > > There is a reason why the temporal database is generated and used
 by default in the PERMANENT directory.
 > > >
 > > > Does it handle the case where the user lacks the filesystem
 permissions to write to PERMANENT?
 > >
 > > There is no explicit error handling implemented. The creation process
 will terminate with a Python exception.
 >
 > Here in our shared /network and multi-user grassdata/ we have exactly
 this problem:
 > while I am the PERMANENT owner, my colleague cannot write into the DB.
 >
 > As a compromise, t.create should advertise t.connnect as a solution to
 the problem, otherwise
 > users get immediately stuck.

 Please try r60732, i have improved the error messages in case the database
 creation or access fails. Database connection failures will now result in
 a fatal error rather then Python traceback.

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/2258#comment:8>
GRASS GIS <http://grass.osgeo.org>



More information about the grass-dev mailing list