|
|
|
Greg Boone
|
Some javascript/style in this post has been disabled (why?)
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 [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-internals |
||||||||||||||||
|
Chris Erickson-2
|
Some javascript/style in this post has been disabled (why?)
Does RC2 contain the long text
field fixes in ArcSDE? Do you know when it might be posted?
From:
[hidden email]
[mailto:[hidden email]] On Behalf Of Greg Boone 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 [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-internals |
|
Greg Boone
|
Some javascript/style in this post has been disabled (why?)
Yes, It will contain that fix. ETA
is towards the end of the week. Thursday or Friday depends on requests for
additional changes. Greg From:
[hidden email]
[mailto:[hidden email]] On Behalf Of Chris
Erickson Does RC2 contain the long text
field fixes in ArcSDE? Do you know when it might be posted?
From:
[hidden email]
[mailto:[hidden email]] On Behalf Of Greg Boone 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 [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-internals |
||||||||||||||||||
|
Jackie Ng
|
In reply to this post
by Greg Boone
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
|
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: [hidden email] [mailto:[hidden email]] On Behalf Of Jackie Ng Sent: Monday, October 05, 2009 6:52 PM To: [hidden email] 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 > [hidden email] > 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 [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-internals _______________________________________________ fdo-internals mailing list [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-internals |
||||||||||||||||
|
Jackie Ng
|
Hi Greg,
I've attached the C# source to that ticket. (w/ updated details) - Jackie
|
||||||||||||||||
|
Greg Boone
|
OK... I have a fix for this. It will go into 3.4.1.
-----Original Message----- From: [hidden email] [mailto:[hidden email]] On Behalf Of Jackie Ng Sent: Tuesday, October 06, 2009 9:57 AM To: [hidden email] 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: [hidden email] > [mailto:[hidden email]] On Behalf Of Jackie Ng > Sent: Monday, October 05, 2009 6:52 PM > To: [hidden email] > 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 >> [hidden email] >> 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 > [hidden email] > http://lists.osgeo.org/mailman/listinfo/fdo-internals > _______________________________________________ > fdo-internals mailing list > [hidden email] > 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 [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-internals _______________________________________________ fdo-internals mailing list [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-internals |
||||||||||||||||
|
Chris Erickson-2
|
In reply to this post
by Greg Boone
Some javascript/style in this post has been disabled (why?)
Is there any update on the
timeline for RC2?
From:
[hidden email]
[mailto:[hidden email]] On Behalf Of Greg Boone Yes, It will contain that fix.
ETA is towards the end of the week. Thursday or Friday depends on requests for
additional changes. Greg From:
[hidden email]
[mailto:[hidden email]] On Behalf Of Chris
Erickson Does RC2 contain the long text
field fixes in ArcSDE? Do you know when it might be posted?
From:
[hidden email]
[mailto:[hidden email]] On Behalf Of Greg Boone 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 [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-internals |
||||||||||||||||||||
|
Greg Boone
|
Some javascript/style in this post has been disabled (why?)
The second RC has been delayed.
I have no ETA on the release of the RC at this time. From:
[hidden email]
[mailto:[hidden email]] On Behalf Of Chris
Erickson Is there any update on the
timeline for RC2?
From:
[hidden email]
[mailto:[hidden email]] On Behalf Of Greg Boone Yes, It will contain that fix.
ETA is towards the end of the week. Thursday or Friday depends on requests for
additional changes. Greg From:
[hidden email] [mailto:[hidden email]]
On Behalf Of Chris Erickson Does RC2 contain the long text
field fixes in ArcSDE? Do you know when it might be posted?
From:
[hidden email]
[mailto:[hidden email]] On Behalf Of Greg Boone 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 [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-internals |
||||||||||||||||||||
|
Chris Erickson-2
|
Some javascript/style in this post has been disabled (why?)
Is there a fundamental reason
why? We may build the fdo provider and go with RC1 on our own, but would like
to know if there are big underlying problems…
From:
[hidden email]
[mailto:[hidden email]] On Behalf Of Greg Boone The second RC has been delayed.
I have no ETA on the release of the RC at this time. From:
[hidden email]
[mailto:[hidden email]] On Behalf Of Chris Erickson Is there any update on the
timeline for RC2?
From:
[hidden email] [mailto:[hidden email]]
On Behalf Of Greg Boone Yes, It will contain that fix.
ETA is towards the end of the week. Thursday or Friday depends on requests for
additional changes. Greg From:
[hidden email]
[mailto:[hidden email]] On Behalf Of Chris
Erickson Does RC2 contain the long text
field fixes in ArcSDE? Do you know when it might be posted?
From:
[hidden email]
[mailto:[hidden email]] On Behalf Of Greg Boone 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 [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-internals |
||||||||||||||||||||||
|
Greg Boone
|
Some javascript/style in this post has been disabled (why?)
At current the build release
process is not fully automated. I may not have the cycles to produce a build
for the next week or so. Greg From:
[hidden email]
[mailto:[hidden email]] On Behalf Of Chris
Erickson Is there a fundamental reason
why? We may build the fdo provider and go with RC1 on our own, but would
like to know if there are big underlying problems…
From:
[hidden email] [mailto:[hidden email]]
On Behalf Of Greg Boone The second RC has been delayed.
I have no ETA on the release of the RC at this time. From:
[hidden email]
[mailto:[hidden email]] On Behalf Of Chris
Erickson Is there any update on the
timeline for RC2?
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Greg Boone Yes, It will contain that fix. ETA
is towards the end of the week. Thursday or Friday depends on requests for
additional changes. Greg From:
[hidden email]
[mailto:[hidden email]] On Behalf Of Chris
Erickson Does RC2 contain the long text
field fixes in ArcSDE? Do you know when it might be posted?
From:
[hidden email]
[mailto:[hidden email]] On Behalf Of Greg Boone 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 [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-internals |
||||||||||||||||||||||
|
Greg Boone
|
Some javascript/style in this post has been disabled (why?)
Hi All, FDO 3.4.1 RC2 has been posted to
http://fdo.osgeo.org/content/fdo-341-downloads Please take a look and if there
are issue, let me know. Greg From:
[hidden email]
[mailto:[hidden email]] On Behalf Of Greg Boone At current the build release
process is not fully automated. I may not have the cycles to produce a build
for the next week or so. Greg From:
[hidden email]
[mailto:[hidden email]] On Behalf Of Chris Erickson Is there a fundamental reason
why? We may build the fdo provider and go with RC1 on our own, but would
like to know if there are big underlying problems…
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Greg Boone The second RC has been delayed.
I have no ETA on the release of the RC at this time. From:
[hidden email]
[mailto:[hidden email]] On Behalf Of Chris
Erickson Is there any update on the
timeline for RC2?
From:
[hidden email]
[mailto:[hidden email]] On Behalf Of Greg Boone Yes, It will contain that fix.
ETA is towards the end of the week. Thursday or Friday depends on requests for
additional changes. Greg From:
[hidden email] [mailto:[hidden email]]
On Behalf Of Chris Erickson Does RC2 contain the long text
field fixes in ArcSDE? Do you know when it might be posted?
From:
[hidden email] [mailto:[hidden email]]
On Behalf Of Greg Boone 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 [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-internals |
||||||||||||||||||||||
|
Crispin_at_1Spatial
|
Hi,
I notice that the last KingOra submission looks like it ties in with KO 0.8.8 http://www.sl-king.com/fdooracle/fdooracle.html There have been a couple of KO releases since then - Haris, is it possible to get the 0.8.9 and 0.8.10 changes in to 3.4.1 before the final release so there is a consistent version between the OSGeo builds downloads on SL-King?
|
||||||||||||||||
|
Haris Kurtagic
|
0.8.9 and 0.8.10 already include direct SDE support. So if I submit it will be together with changes for direct SDE RFC. I can do that ? Haris -----Original Message----- From: [hidden email] [mailto:[hidden email]] On Behalf Of Crispin_at_1Spatial Sent: Sunday, November 08, 2009 10:47 AM To: [hidden email] Subject: RE: [fdo-internals] FDO 3.4.1 RC2 -- KingOra Version Hi, I notice that the last KingOra submission looks like it ties in with KO 0.8.8 http://www.sl-king.com/fdooracle/fdooracle.html http://www.sl-king.com/fdooracle/fdooracle.html There have been a couple of KO releases since then - Haris, is it possible to get the 0.8.9 and 0.8.10 changes in to 3.4.1 before the final release so there is a consistent version between the OSGeo builds downloads on SL-King? Greg Boone wrote: > > Hi All, > > FDO 3.4.1 RC2 has been posted to > > http://fdo.osgeo.org/content/fdo-341-downloads > > Please take a look and if there are issue, let me know. > > Greg > > From: [hidden email] > [mailto:[hidden email]] On Behalf Of Greg Boone > Sent: Tuesday, October 13, 2009 7:17 PM > To: FDO Internals Mail List > Subject: [fdo-internals] RE: FDO 3.4.1 RC2 > > At current the build release process is not fully automated. I may not > have the cycles to produce a build for the next week or so. > > Greg > > From: [hidden email] > [mailto:[hidden email]] On Behalf Of Chris Erickson > Sent: Tuesday, October 13, 2009 4:00 PM > To: FDO Internals Mail List > Subject: [fdo-internals] RE: FDO 3.4.1 RC2 > > Is there a fundamental reason why? We may build the fdo provider and go > with RC1 on our own, but would like to know if there are big underlying > problems... > > [cid:[hidden email]]<http://www.cartopac.com/> > > chris erickson > developer > [hidden email]<mailto:[hidden email]> > 970.493.9500 x 191 > 970.482.1485 (fax) > > > > From: [hidden email] > [mailto:[hidden email]] On Behalf Of Greg Boone > Sent: Tuesday, October 13, 2009 12:14 PM > To: FDO Internals Mail List > Subject: [fdo-internals] RE: FDO 3.4.1 RC2 > > The second RC has been delayed. I have no ETA on the release of the RC at > this time. > > From: [hidden email] > [mailto:[hidden email]] On Behalf Of Chris Erickson > Sent: Monday, October 12, 2009 10:35 AM > To: FDO Internals Mail List > Subject: [fdo-internals] RE: FDO 3.4.1 RC2 > > Is there any update on the timeline for RC2? > > [cid:[hidden email]]<http://www.cartopac.com/> > > chris erickson > developer > [hidden email]<mailto:[hidden email]> > 970.493.9500 x 191 > 970.482.1485 (fax) > > > > From: [hidden email] > [mailto:[hidden email]] On Behalf Of Greg Boone > Sent: Monday, October 05, 2009 3:39 PM > To: FDO Internals Mail List > Subject: [fdo-internals] RE: FDO 3.4.1 RC2 > > Yes, It will contain that fix. ETA is towards the end of the week. > Thursday or Friday depends on requests for additional changes. > > Greg > > From: [hidden email] > [mailto:[hidden email]] On Behalf Of Chris Erickson > Sent: Monday, October 05, 2009 5:35 PM > To: FDO Internals Mail List > Subject: [fdo-internals] RE: FDO 3.4.1 RC2 > > Does RC2 contain the long text field fixes in ArcSDE? Do you know when it > might be posted? > > [cid:[hidden email]]<http://www.cartopac.com/> > > chris erickson > developer > [hidden email]<mailto:[hidden email]> > 970.493.9500 x 191 > 970.482.1485 (fax) > > > > From: [hidden email] > [mailto:[hidden email]] On Behalf Of Greg Boone > Sent: Monday, October 05, 2009 2:32 PM > To: FDO Internals Mail List > Subject: [fdo-internals] FDO 3.4.1 RC2 > > 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 > [hidden email] > http://lists.osgeo.org/mailman/listinfo/fdo-internals > > -- View this message in context: http://n2.nabble.com/FDO-3-4-1-RC2-tp3771453p3967609.html Sent from the FDO Internals mailing list archive at Nabble.com. _______________________________________________ fdo-internals mailing list [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-internals _______________________________________________ fdo-internals mailing list [hidden email] http://lists.osgeo.org/mailman/listinfo/fdo-internals |
||||||||||||||||
|
Crispin_at_1Spatial
|
>> 0.8.9 and 0.8.10 already include direct SDE support. I guess I was just thinking the two issues you describe on your site (NULL metadata and connection type) could be as partial individual file submissions. If we could get RFC 42 to be assigned a guide and voted on I don't mind the submission to trunk - notwithstanding the two small(?) outstanding I think the assignment/approval/voting timeline may prohibit this. And, strictly RFC42 is a new feature that should not come in at the RC build level. Crispin
|
||||||||||||||||
| Free Embeddable Forum Powered by Nabble | Help |