[Qgis-developer] [GRASS-dev] New GRASS plugin: a test drive

Radim Blazek radim.blazek at gmail.com
Wed Oct 7 23:43:35 PDT 2015


So it will be my local problem.

Thanks
Radim

On Wed, Oct 7, 2015 at 8:27 PM, Maris Nartiss <maris.gis at gmail.com> wrote:
> There is a difference between "should" and "does".
>
> DB is not a file in mapset, as PostgreSQL is also a valid DB backend.
> In case of DBF, there will be more than one file etc.
>
> As others have pointed out - such functionality seems to work, thus
> your observed failure could indicate on a bug or platform/backend
> quirk (I have seen failures due to path encoding on Windows, antivirus
> program blocking etc.).
> Classical source of problems also is "delete while open" approach for
> files as it works on nix but not on Windows.
>
> Thus information on DB, OS could be important.
>
> All best,
> Māris.
>
>
>
> 2015-10-07 11:38 GMT+03:00 Radim Blazek <radim.blazek at gmail.com>:
>> On Wed, Oct 7, 2015 at 7:01 AM, Maris Nartiss <maris.gis at gmail.com> wrote:
>>> Radim,
>>> please provide information on source / target database (DBFs?
>>> SQLite?); Are permissions set correctly? OS (Windows)?
>>
>> Normally, you don't need to care about database, GRASS should do
>> everything for you behind the scenes. By default, the DB is created as
>> a file inside the mapset, for which you must have write permission by
>> definition.
>>
>> Radim


More information about the Qgis-developer mailing list