Opened 16 years ago
Closed 9 years ago
#2267 closed defect (wontfix)
ogrinfo should not open datasources in write/append mode
Reported by: | hobu | Owned by: | warmerdam |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | default | Version: | unspecified |
Severity: | normal | Keywords: | |
Cc: | Daniel Morissette, Even Rouault |
Description
Frank,
Why does ogrinfo open datasources in update mode by default? I know there's the -ro switch to silence the noise, but for the SDE driver, I would like to depend on the fact that when a DataSource is opened for update I can go ahead and fire up the SDE state/version handling facilities. A simple ogrinfo without the -ro command in that case is going to have unintended consequences (pushing forward the edit state for the version queried). Can I depend on opening a DataSource for update having this kind of behavior (I'm quite screwed if I can't, actually), and if so, what is the argument for keeping ogrinfo opening in update mode?
Howard
Change History (6)
comment:1 by , 16 years ago
Cc: | added |
---|
comment:2 by , 16 years ago
Cc: | added |
---|
comment:4 by , 16 years ago
Personally, since the command is called ogrinfo and not ogrupdate, I think we should default to read-only even if -sql is used. It should be up to the caller to use -rw if they use a SQL statement that requires update access.
comment:5 by , 10 years ago
Six more years gone with current behaviour with not much noise. Is there still pressure to change the default in GDAL 2.0?
comment:6 by , 9 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Let's see if closing this ticket makes someone to react.