SuperKaioken / odbc2kml

Automatically exported from code.google.com/p/odbc2kml
0 stars 0 forks source link

changing DB to DB with different tables handled poorly. #145

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Edit your oracle db on the vm.
2. Add a new table: NEWTABLE
3. Add columns to NEWTABLE: FIRST and SECOND, both holding integers.
4. Make a new connection, pointing to your oracle server on the VM.
5. Set up mapping (lat/long and placemark), description, icon and overlay 
conditions, all pointing to NEWTABLE.FIRST and NEWTABLE.SECOND.
6. Save the connection.
7. Modify the connection to point to your MySQL db on the vm.

What is the expected output? What do you see instead?
Expected: mapping, description, and conditions with NEWTABLE referenced 
should all be removed.

Actual: Only  description is removed.

Please use labels and text to provide additional information.

Original issue reported on code.google.com by mbbowser@gmail.com on 8 Apr 2010 at 12:34

GoogleCodeExporter commented 9 years ago

Original comment by mbbowser@gmail.com on 8 Apr 2010 at 12:36

GoogleCodeExporter commented 9 years ago
To clarify, the mapping and conditions still have their references to 
NEWTABLE.FIRST 
and NEWTABLE.SECOND.

Original comment by mbbowser@gmail.com on 8 Apr 2010 at 12:37

GoogleCodeExporter commented 9 years ago
One condition did get removed, the rest remained. This part might have actually 
been a 
bug, though. I thought I saw a condition get removed unintentionally. Looking 
into 
that...

Original comment by mbbowser@gmail.com on 8 Apr 2010 at 12:38

GoogleCodeExporter commented 9 years ago
Set purge to set mapping to new mapping when purge is true. Multiple conditions
should now remove, counter was not being adjusted properly.

Original comment by Ctan...@gmail.com on 8 Apr 2010 at 2:21

GoogleCodeExporter commented 9 years ago

Original comment by mbbowser@gmail.com on 8 Apr 2010 at 2:35