[GRASSLIST:10569] Re: v.in.db problems

[Ing.Peter Misovic]

Yes it is little bit confusing. I had the same problem nad I don't
really like it. The only solution I found is to add layer with OGR
(v.in.ogr). There is possiblity to not create duplicate attribute
table in DB. But I'm not sure, if it supports MySQL. I've used
PostgreSQL only.


Peter

On 2/24/06, Chris Fonnesbeck <fonnesbeck at gmail.com> wrote:
> >
> > I got that error too, when I gave my new vector the same name as the
> > database table it was reading from. Try giving your output vector a
> > different name so there isn't a conflict of two db tables with the
> > same name.
> >
>
> That would be very awkward if thats the case. I dont want multiple
> copies of the same table in MySQL, I just want the layer to use the
> specified table. There must be a way ...
>
> --
> Chris Fonnesbeck + Atlanta, GA + http://trichech.us
>
>