Opened 17 years ago
Closed 17 years ago
#319 closed defect (fixed)
SQLite: Problematic conversion
| Reported by: | jbirch | Owned by: | traianstanev |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | SQLite Provider | Version: | 3.3.1 |
| Severity: | 3 | Keywords: | |
| Cc: | External ID: |
Description
I was trying to pull out a subset of data for testing with #316 using FME, and managed to create an SDF that breaks either the convertor (using "optimize") or causes an exception in SQLite provider itself if I convert the data source without optimizing.
This file works fine in its native SDF format, and the data converts and works fine as the Easement feature class from the NanaimoCadastre SDF (linked to #316). Something in the FME data transfer process caused it to no longer be acceptable to the SQLite provider; perhaps an attribute data type changed?
Change History (6)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
I wouldn't be at all surprised if I screwed something up in the FME settings. I'll try again, fixing those problems.
Odd that I got errors during optimized conversion when you didn't though. I'll try a clean build on the provider and see if it makes a difference.
Most of the data in my test set probably has a lot of nulls. Those layers were under heavy development when I pulled them out of Oracle a year and a half ago :)
comment:3 by , 17 years ago
Ah, optimized. I was doing regular conversion. I will try optimized now.
comment:4 by , 17 years ago
It's failing at this line:
FdoPtr<FdoIFeatureReader> rdr = select->Execute();
Don't know enough about VS debugging to tell you more than that...
I wonder if this could be because of the mixed environment I'm using? I've "externalled" the SQLite provider into the 3.3.0 tag of FDO.
comment:5 by , 17 years ago
Actually I know what it is. It is because the ID is not marked as autogenerated -- it ends up making a weird filter to ask for a specific feature from the source SDF, and that fails. I know how to fix it.
comment:6 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
It should be fixed now. Reopen if you still have the same problem.
Looks like there a few weird things about the SDF produced by FME. First, the integer ID is not marked as autogenerated, even though it looks like it is. Second, the GISLINK property comes out as REAL even though it should probably be an int. Nevertheless, it converted without errors for me, but it looks strange (lots of null properties). I will send you the converted file to compare.