Some javascript/style in this post has been disabled (
why?)
Greg,
The revision for
uniqueIdentifier support is 4474.
Brent.
From:
[hidden email] [mailto:[hidden email]]
On Behalf Of Greg Boone
Sent: Friday, September 25, 2009 3:56 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] Patch: Issue 549 - UniqueIdentifier Fields
not working in SQL Server Spatial
We can try…
Brent, can I get a list of the
revisions you submitted that are candidates for porting?
Greg
From:
[hidden email]
[mailto:[hidden email]] On Behalf Of Chris
Erickson
Sent: Friday, September 25, 2009 3:50 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] Patch: Issue 549 - UniqueIdentifier Fields
not working in SQL Server Spatial
Ahh,
So, I guess my request is to
backport that to this 3.4.1 version so it would be in the release…along with
the other patch I submitted. Is that possible?
|

|
chris erickson
developer
[hidden email]
970.493.9500 x
191
970.482.1485
(fax)
|
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Brent
Robinson
Sent: Friday, September 25, 2009 1:48 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] Patch: Issue 549 - UniqueIdentifier Fields
not working in SQL Server Spatial
There was a fix done to support
uniqueidentifier columns on Mar. 24 but it was only applied to the trunk and
was not backported to 3.4. At the moment, you’d have to do a separate compile
to get it into a 3.4 provider.
I’m not sure if the fix could
still be backported to 3.4. Greg would have a better idea.
From:
[hidden email]
[mailto:[hidden email]] On Behalf Of Greg Boone
Sent: Friday, September 25, 2009 3:37 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] Patch: Issue 549 - UniqueIdentifier Fields
not working in SQL Server Spatial
This upload can be considered
Release Candidate 1.
From:
[hidden email] [mailto:[hidden email]]
On Behalf Of Greg Boone
Sent: Friday, September 25, 2009 3:35 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] Patch: Issue 549 - UniqueIdentifier Fields
not working in SQL Server Spatial
Today, FDO 3.4.1 was uploaded
to:
http://fdo.osgeo.org/content/fdo-341-downloads
Greg
From:
[hidden email]
[mailto:[hidden email]] On Behalf Of Chris
Erickson
Sent: Friday, September 25, 2009 3:27 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] Patch: Issue 549 - UniqueIdentifier Fields
not working in SQL Server Spatial
Ok, I must have missed that, I
think I must have been looking at something equivalent to the release of 3.4.
Is there a patched/released
version of 3.4 with this in it? (3.4.1?) Or do I need to compile separately.
We need to build a version of
3.4 with both of these changes in it, and I see all sorts of changes committed
to the 3.4 branch – where was the release version of 3.4 built from? All
of the stuff that has been committed to the branch – has that been re-compiled
and re-released? Is this what 3.4.1 is?
|

|
chris erickson
developer
[hidden email]
970.493.9500 x
191
970.482.1485
(fax)
|
From:
[hidden email]
[mailto:[hidden email]] On Behalf Of Brent
Robinson
Sent: Friday, September 25, 2009 1:18 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] Patch: Issue 549 - UniqueIdentifier Fields
not working in SQL Server Spatial
Hi Chris,
I had a look but the trunk
desc_selct.c already has a:
case SQL_GUID
:
a bit further up in the file
(line 187).
Brent.
From:
[hidden email]
[mailto:[hidden email]] On Behalf Of Chris
Erickson
Sent: Friday, September 25, 2009 2:21 PM
To: [hidden email]
Subject: [fdo-internals] Patch: Issue 549 - UniqueIdentifier Fields not
working in SQL Server Spatial
Hello,
I’ve tested the attached patch, and it seems to work.
Can anyone verify it? I’d like to commit it to trunk.
|

|
chris erickson
developer
[hidden email]
970.493.9500 x
191
970.482.1485
(fax)
|
_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals