/*
 *    GeoTools - The Open Source Java GIS Toolkit
 *    http://geotools.org
 *
 *    (C) 2002-2008, Open Source Geospatial Foundation (OSGeo)
 *
 *    This library is free software; you can redistribute it and/or
 *    modify it under the terms of the GNU Lesser General Public
 *    License as published by the Free Software Foundation;
 *    version 2.1 of the License.
 *
 *    This library is distributed in the hope that it will be useful,
 *    but WITHOUT ANY WARRANTY; without even the implied warranty of
 *    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
 *    Lesser General Public License for more details.
 */
package org.geotools.data.db2;

import org.geotools.data.DefaultTransaction;
import org.geotools.data.FeatureWriter;
import org.geotools.data.Transaction;
import org.geotools.data.simple.SimpleFeatureCollection;
import org.geotools.data.simple.SimpleFeatureIterator;
import org.geotools.jdbc.JDBCEmptyGeometryOnlineTest;
import org.geotools.jdbc.JDBCEmptyGeometryTestSetup;
import org.opengis.feature.simple.SimpleFeature;
import org.opengis.feature.simple.SimpleFeatureType;

import com.vividsolutions.jts.geom.Geometry;
import com.vividsolutions.jts.io.WKTReader;

/**
 * 
 *
 */
public class DB2EmptyGeometryOnlineTest extends JDBCEmptyGeometryOnlineTest {

    @Override
    protected JDBCEmptyGeometryTestSetup createTestSetup() {
        return new DB2EmptyGeometryTestSetup(new DB2TestSetup());
    }
    
// TODO - DWA
    /**
     * This method always fails due to fw.write() in the parent class.
     * This is due to some DB2 JDBC functions not working correctly.
     * 
    1. DB2SQLDialect should implement lookupGeneratedValuesPostInsert(), returning true so that key columns are not included in 
      the insert operation when the primary key is autogenerated.
    2. When this change is made, JDBCDataStore::insertPS uses cx.prepareStatement(sql, keysFetcher.getColumnNames())
      in order to tell DB2 which columns to get autogenerated key values for. Unfortunately, when the key column name
      is lower-case, DB2 defaults to the upper-case value and the ps.AddBatch() for the insert subsequently fails with SQLCODE -206 because the upper-case value
      doesn't match the actual lower-case key column name. This fails at ps.addBatch() in JDBCDataStore::insertPS
    3. Changing the primary key to upper-case (FID), allows ps.addBatch to succeed and then KeysFetcher::postInsert is called but 
      this fails due to ps.getGeneratedKeys() which is broken when ps.AddBatch() is used. The ResultSet is empty
      instead of returning the keys which causes subsequent failures. This is known by the DB2 JDBC 
      development team but is not likely to be fixed.
    4. Changing the primary key to upper-case is not viable because JDBCInsertFeatureWriter::flush() has the primary key
      hard-coded as "fid".    
    It would be better just to override JDBCEmptyGeometryOnlineTest::testInsertEmptyGeometry but this is declared private.  
     */    
    @Override
    public void testEmptyPoint() throws Exception {
    }
    @Override
    public void testEmptyLine() throws Exception {
    }
    @Override
    public void testEmptyPolygon() throws Exception {
    }
    @Override
    public void testEmptyMultiPoint() throws Exception {
    }
    @Override
    public void testEmptyMultiLine() throws Exception {
    }
    @Override
    public void testEmptyMultiPolygon() throws Exception {
    }


}