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
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@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
From my point of view it is not bug but just I don't see why new
attribe table has to be created in case of building vector from
database. I always thougt (till I found out) that vector file is
placed on hdd (cretated on database table) and all attributes are in
original db table. I don't see why to create duplicate table in that
case. And I always thougt that if I change database attribute (f.e X)
for this file, also vector file will be effected.
You don't need to know too much about DB just imagine, how
unconfortable it is If you create 34 vectors ==> 34 new db tables.
So I don't know if we can report wish into bugtracking system. Can we ?
Thank you,
Peter
On 2/26/06, Maciek Sieczka <werchowyna@epf.pl> wrote:
On Sat, 25 Feb 2006 14:33:15 +0100
"Ing.Peter Misovic" <peter.misovic@gmail.com> wrote:Guys,
If you are sure this is a bug, please report it to the bugtracker so
developers won't loose the track of it. Or consider requesting it as a
wish if it is rather a missing feature than an error in the current
program. I can't decide myself as I don't know to much about DBs.> 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@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
> >
> >
>
>--------------------
W polskim Internecie s? setki milion?w stron. My przekazujemy Tobie tylko najlepsze z nich!
http://katalog.panoramainternetu.pl/