[fdo-internals] FDO 3.4.1 RC2

Greg Boone greg.boone at autodesk.com
Tue Oct 6 22:16:01 EDT 2009


OK... I have a fix for this. It will go into 3.4.1.

-----Original Message-----
From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Jackie Ng
Sent: Tuesday, October 06, 2009 9:57 AM
To: fdo-internals at lists.osgeo.org
Subject: RE: [fdo-internals] FDO 3.4.1 RC2


Hi Greg,

I've attached the C# source to that ticket. (w/ updated details)

- Jackie


Greg Boone wrote:
> 
> Jackie,
> 
> I ran the ODBC Describe Schema Test below and everything seemed fine. Send
> me the code for the test that you ran and I will see what I can find.
> 
> 
> Output from Test:
> 
> OdbcAccessDescribeSchemaTest.describeWithClassNames (10/06/09 09:11:20):
> Setting Current schema to be 'Fdo'
> Current schema 'Fdo'
> Current class 'Cities'
> Current class 'VIEW1'
> 
> Test:
> 
> void OdbcAccessDescribeSchemaTest::describeWithClassNames()
> {
>     try
>     {
>         // call the static method
>         FdoPtr<FdoIConnection> connection =
> UnitTestUtil::GetProviderConnectionObject();
>         if (connection == NULL)
>             CPPUNIT_FAIL("FAILED - CreateConnection returned NULL\n");
> 
>         // Now open the database with the given 
>         connection->SetConnectionString(GetConnectString());
>         connection->Open();
> 
>         // Now analyse the schema with the mappings in place.
>         // This is a modified version of DescribeSchemaTest::SchemaTest().
>         FdoPtr<FdoIDescribeSchema> describeSchemaCmd =
>            
> (FdoIDescribeSchema*)connection->CreateCommand(FdoCommandType_DescribeSchema);
> 
> 	  wprintf(L"Setting Current schema to be '%ls'\n", L"Fdo");
>         describeSchemaCmd->SetSchemaName(L"Fdo");
> 
>         FdoPtr<FdoStringCollection> classNames =
> FdoStringCollection::Create();
>         classNames->Add(L"Cities");
>         classNames->Add(L"VIEW1");
>         describeSchemaCmd->SetClassNames(classNames);
>         FdoPtr<FdoFeatureSchemaCollection> schemas =
> describeSchemaCmd->Execute();
> 
>         if (schemas == NULL)
>             CPPUNIT_FAIL("FAILED - DescribeSchema returned NULL
> collection\n");
> 
>         FdoInt32 numSchemas = schemas->GetCount();
>         for (int i=0; i<numSchemas; i++)
>         {
>             FdoPtr<FdoFeatureSchema> schema = schemas->GetItem(i);
> 
>             FdoString* schemaName = schema->GetName();
> 			wprintf(L"Current schema '%ls'\n", schemaName);
>             FdoPtr<FdoClassCollection> classes = schema->GetClasses();
> 
>             FdoInt32 numClasses = classes->GetCount();
>             CPPUNIT_ASSERT(numClasses == 2);
>             for (int j=0; j<numClasses; j++)
>             {
>                 // Note the assumption here that it is a feature class (it
> is set up so
>                 // in the test data).
>                 FdoPtr<FdoClassDefinition> classDef = classes->GetItem(j);
> 
>                 // analyze the feature class
>                 FdoString* className = classDef->GetName();
>     			wprintf(L"Current class '%ls'\n", className);
>             }
>         }
>     }
>     catch (FdoException *ex)
>     {
> 		TestCommonFail (ex);
>     }
> 
> }
> 
> 
> 
> -----Original Message-----
> From: fdo-internals-bounces at lists.osgeo.org
> [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Jackie Ng
> Sent: Monday, October 05, 2009 6:52 PM
> To: fdo-internals at lists.osgeo.org
> Subject: Re: [fdo-internals] FDO 3.4.1 RC2
> 
> 
> Hi Greg,
> 
> I don't know if you had a look at this one, but there is a major defect
> with
> the enhanced IDescribeSchema command when used against any GenericRdbms
> provider, where it scrambles the input class name(s). This defect make the
> enhanced IDescribeSchema command unusable.
> 
> http://trac.osgeo.org/fdo/ticket/552
> 
> - Jackie
> 
> 
> 
> Greg Boone wrote:
>> 
>> Hi All,
>> 
>> I am considering releasing FDO 3.4.1 RC2 later this week. Are there any
>> outstanding defects that have been resolved in trunk that need porting
>> back to 3.4.1? Are there any show-stopper issues that remain in 3.4.1
>> before the next release candidate is published?
>> 
>> Greg
>> 
>> _______________________________________________
>> fdo-internals mailing list
>> fdo-internals at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/fdo-internals
>> 
>> 
> 
> -- 
> View this message in context:
> http://n2.nabble.com/FDO-3-4-1-RC2-tp3771453p3772133.html
> Sent from the FDO Internals mailing list archive at Nabble.com.
> _______________________________________________
> fdo-internals mailing list
> fdo-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/fdo-internals
> _______________________________________________
> fdo-internals mailing list
> fdo-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/fdo-internals
> 
> 

-- 
View this message in context: http://n2.nabble.com/FDO-3-4-1-RC2-tp3771453p3775178.html
Sent from the FDO Internals mailing list archive at Nabble.com.
_______________________________________________
fdo-internals mailing list
fdo-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fdo-internals


More information about the fdo-internals mailing list