FEATID is an identity property and lives in a RDBMS. It is a primary key and
is indexed and table is only 250 records right now.
It takes a total of 7-8 seconds to post to the db, get the feat id, then
connect to the DB to update the coordinates for the associated label point.
What i was really
...@lists.osgeo.org] On Behalf Of tmblackflag
Sent: Wednesday, November 09, 2011 12:13 PM
To: mapguide-users@lists.osgeo.org
Subject: [mapguide-users] Re: Client side way to get FEATID's from FDO?
FEATID is an identity property and lives in a RDBMS. It is a primary key and
is indexed and table is only 250
1) Yes but i'm switching it over to a one click move as recommended.
2) The feature source was created via Map 3d's schema editor with all keys
and indexes automatically created by the tool. I've verified everything is
there. Here is my complete server side code to make this happen. While it
Have you done any profiling (eg. Measure time before/after the calls) to make
sure that this is the case?
Something is very wrong if a single query/readnext of the reader is very
slow.
- Jackie
--
View this message in context:
It could be a datastore problem.
Is FEATID an identity property?
If it is not, is your feature source pointing to an RDBMS? If so, is the
FEATID column indexed?
The selection filter could be causing table scans if the column is not
PK/indexed, whose slowness would be noticeable on a very large
