The following comment has been added to this issue:
Author: Andrea Aime
Created: Sat, 24 Apr 2004 11:02 AM
Body:
This bug has been solved in fid_exp. It is due to a bug into the jdbc driver
I think, and I've solved by opening the result set in read only mode and
creating explicit queries for delete and update (explicit ones for insert
where already there)
What a nice move:
But I love that use of the API - strikes me as fairly maintainable. I look
forward to jumping on fid_exp to have a look.
This diverges from the origional version of the FeatureWriter serving as direct
access to the ResultSet. It is however more in line with the approach Shapefile
uses.
Alle 22:17, sabato 24 aprile 2004, jgarnett@anonymised.com ha scritto:
Quoting jira@anonymised.com:
> The following comment has been added to this issue:
>
> Author: Andrea Aime
> Created: Sat, 24 Apr 2004 11:02 AM
> Body:
> This bug has been solved in fid_exp. It is due to a bug into the jdbc
> driver I think, and I've solved by opening the result set in read only
> mode and creating explicit queries for delete and update (explicit ones
> for insert where already there)
What a nice move:
But I love that use of the API - strikes me as fairly maintainable. I look
forward to jumping on fid_exp to have a look.
This diverges from the origional version of the FeatureWriter serving as
direct access to the ResultSet.
It was however impossible to use it as intended since when loading geometric
data we convert it to a WKT representation by using a function, making the
result set not updatable... is there any way to parse the "raw" geometric
function without the need to convert it to WKT or WKB? If so, the result set
could be used (maybe) as you planned to, as an updatable one.