RFC 26 - New Extended Select command and Scrollable Reader - for review

[Orest Halustchak]

Some javascript/style in this post has been disabled (why?)

Hi,

 

I’d like to bring your attention to RFC 26 ( http://trac.osgeo.org/fdo/wiki/FDORfc26 ) which proposes to add a new Extended Select command with uses a Scrollable feature reader. Basically, this takes what currently are custom commands in the SDF, SHP, and recently SQLite providers and makes them generic FDO commands. This will remove special case handling for applications that currently use these and open the door for generic use by any application.

 

Please review and provide your feedback.

 

Thanks,

Orest.

 

_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals

[Orest Halustchak]

Some javascript/style in this post has been disabled (why?)

Hi,

 

I wonder if anyone has any comments on this. If nobody has any objections to it, I’d like to bring it to a vote soon.

 

Thanks,

Orest.

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Orest Halustchak
Sent: Friday, October 17, 2008 12:37 PM
To: FDO Internals Mail List
Subject: [fdo-internals] RFC 26 - New Extended Select command and Scrollable Reader - for review

 

Hi,

 

I’d like to bring your attention to RFC 26 ( http://trac.osgeo.org/fdo/wiki/FDORfc26 ) which proposes to add a new Extended Select command with uses a Scrollable feature reader. Basically, this takes what currently are custom commands in the SDF, SHP, and recently SQLite providers and makes them generic FDO commands. This will remove special case handling for applications that currently use these and open the door for generic use by any application.

 

Please review and provide your feedback.

 

Thanks,

Orest.

 

_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals

[Jason Birch]

Some javascript/style in this post has been disabled (why?)

I don’t have any direct experience with this because MapGuide doesn’t currently doesn’t allow access to these commands.  I certainly see value in making these part of the common feature set though.  Maybe I’ll eventually be able to do sorting on SDF results via MapGuide J

 

One thing that occurred to me when reading this RFC was that I’d like to see a mechanism to “page” through results; similar to the LIMIT clause in MySQL.  When displaying result sets in a web environment, you often want to give the user a small set of the data, and then page through the results N records at a time.  I can currently brute-force this, but it would be more efficient to handle this on the FDO side, especially for providers where the underlying storage format has optimized methods of dealing with it.  The current enhancements would make this more efficient to brute-force, but I wonder if adding parameters to the initial selection (start record, number of results) would make this even more efficient.

 

Jason

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Orest Halustchak
Sent: Monday, October 20, 2008 11:24
To: FDO Internals Mail List
Subject: RE: [fdo-internals] RFC 26 - New Extended Select command andScrollable Reader - for review

 

Hi,

 

I wonder if anyone has any comments on this. If nobody has any objections to it, I’d like to bring it to a vote soon.

 

Thanks,

Orest.

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Orest Halustchak
Sent: Friday, October 17, 2008 12:37 PM
To: FDO Internals Mail List
Subject: [fdo-internals] RFC 26 - New Extended Select command and Scrollable Reader - for review

 

Hi,

 

I’d like to bring your attention to RFC 26 ( http://trac.osgeo.org/fdo/wiki/FDORfc26 ) which proposes to add a new Extended Select command with uses a Scrollable feature reader. Basically, this takes what currently are custom commands in the SDF, SHP, and recently SQLite providers and makes them generic FDO commands. This will remove special case handling for applications that currently use these and open the door for generic use by any application.

 

Please review and provide your feedback.

 

Thanks,

Orest.

 

_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals

[Jason Birch]

Some javascript/style in this post has been disabled (why?)

I should make it clear that my pondering about paging is not something that I’m asking to have added to the current RFC.

 

Jason

 

From: Jason Birch
Subject: RE: [fdo-internals] RFC 26 - New Extended Select commandandScrollable Reader - for review

 

One thing that occurred to me when reading this RFC was that I’d like to see a mechanism to “page” through results.

_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals

[Orest Halustchak]

Some javascript/style in this post has been disabled (why?)

Hi Jason,

 

So, this limit would be something that would return an end of fetch after reading ‘limit’ number of records? But, then you can reset it I guess when you want to get the next page (maybe just by calling ReadAtIndex() again). An issue with the scrollable reader is that you can read forwards or backwards, and jump to a new record index at any time. So, I think adding a limit would complicate this mechanism – knowing when to reset it or what it means after jumping to a new record.

 

Thanks,

Orest.

 

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Jason Birch
Sent: Monday, October 20, 2008 3:03 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] RFC 26 - New Extended Select command andScrollable Reader - for review

 

I don’t have any direct experience with this because MapGuide doesn’t currently doesn’t allow access to these commands.  I certainly see value in making these part of the common feature set though.  Maybe I’ll eventually be able to do sorting on SDF results via MapGuide J

 

One thing that occurred to me when reading this RFC was that I’d like to see a mechanism to “page” through results; similar to the LIMIT clause in MySQL.  When displaying result sets in a web environment, you often want to give the user a small set of the data, and then page through the results N records at a time.  I can currently brute-force this, but it would be more efficient to handle this on the FDO side, especially for providers where the underlying storage format has optimized methods of dealing with it.  The current enhancements would make this more efficient to brute-force, but I wonder if adding parameters to the initial selection (start record, number of results) would make this even more efficient.

 

Jason

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Orest Halustchak
Sent: Monday, October 20, 2008 11:24
To: FDO Internals Mail List
Subject: RE: [fdo-internals] RFC 26 - New Extended Select command andScrollable Reader - for review

 

Hi,

 

I wonder if anyone has any comments on this. If nobody has any objections to it, I’d like to bring it to a vote soon.

 

Thanks,

Orest.

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Orest Halustchak
Sent: Friday, October 17, 2008 12:37 PM
To: FDO Internals Mail List
Subject: [fdo-internals] RFC 26 - New Extended Select command and Scrollable Reader - for review

 

Hi,

 

I’d like to bring your attention to RFC 26 ( http://trac.osgeo.org/fdo/wiki/FDORfc26 ) which proposes to add a new Extended Select command with uses a Scrollable feature reader. Basically, this takes what currently are custom commands in the SDF, SHP, and recently SQLite providers and makes them generic FDO commands. This will remove special case handling for applications that currently use these and open the door for generic use by any application.

 

Please review and provide your feedback.

 

Thanks,

Orest.

 

_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals

[Jason Birch]

Some javascript/style in this post has been disabled (why?)

I was thinking something that limited the total records that were returned; everything outside of the limit window (start record, num rows) would not be accessible via the api at all.  Additional results would require a second select.  This might be a better fit for the standard select than the scrollable reader?

 

To clarify, in SQL I would do something like this for the first page of results:

 

SELECT id, name

FROM tablename

LIMIT 0,20

 

And this for the second page:

 

SELECT id, name

FROM tablename

LIMIT 20,20

 

Etc, etc,

 

Because HTTP is stateless, there is no reason to make rows outside of the selected set available, unless there is some kind of feature cache at the FDO level that would make subsequent selects more efficient.

 

Jason

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Orest Halustchak
Sent: Monday, October 20, 2008 12:49
To: FDO Internals Mail List
Subject: RE: [fdo-internals] RFC 26 - New Extended Select commandandScrollable Reader - for review

 

Hi Jason,

 

So, this limit would be something that would return an end of fetch after reading ‘limit’ number of records? But, then you can reset it I guess when you want to get the next page (maybe just by calling ReadAtIndex() again). An issue with the scrollable reader is that you can read forwards or backwards, and jump to a new record index at any time. So, I think adding a limit would complicate this mechanism – knowing when to reset it or what it means after jumping to a new record.

 

Thanks,

Orest.

 

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Jason Birch
Sent: Monday, October 20, 2008 3:03 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] RFC 26 - New Extended Select command andScrollable Reader - for review

 

I don’t have any direct experience with this because MapGuide doesn’t currently doesn’t allow access to these commands.  I certainly see value in making these part of the common feature set though.  Maybe I’ll eventually be able to do sorting on SDF results via MapGuide J

 

One thing that occurred to me when reading this RFC was that I’d like to see a mechanism to “page” through results; similar to the LIMIT clause in MySQL.  When displaying result sets in a web environment, you often want to give the user a small set of the data, and then page through the results N records at a time.  I can currently brute-force this, but it would be more efficient to handle this on the FDO side, especially for providers where the underlying storage format has optimized methods of dealing with it.  The current enhancements would make this more efficient to brute-force, but I wonder if adding parameters to the initial selection (start record, number of results) would make this even more efficient.

 

Jason

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Orest Halustchak
Sent: Monday, October 20, 2008 11:24
To: FDO Internals Mail List
Subject: RE: [fdo-internals] RFC 26 - New Extended Select command andScrollable Reader - for review

 

Hi,

 

I wonder if anyone has any comments on this. If nobody has any objections to it, I’d like to bring it to a vote soon.

 

Thanks,

Orest.

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Orest Halustchak
Sent: Friday, October 17, 2008 12:37 PM
To: FDO Internals Mail List
Subject: [fdo-internals] RFC 26 - New Extended Select command and Scrollable Reader - for review

 

Hi,

 

I’d like to bring your attention to RFC 26 ( http://trac.osgeo.org/fdo/wiki/FDORfc26 ) which proposes to add a new Extended Select command with uses a Scrollable feature reader. Basically, this takes what currently are custom commands in the SDF, SHP, and recently SQLite providers and makes them generic FDO commands. This will remove special case handling for applications that currently use these and open the door for generic use by any application.

 

Please review and provide your feedback.

 

Thanks,

Orest.

 

_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals

[Orest Halustchak]

Some javascript/style in this post has been disabled (why?)

Hi Jason,

 

Yes, I think this might work better in the standard select with regular forward-only reader.

 

Orest.

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Jason Birch
Sent: Monday, October 20, 2008 4:06 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] RFC 26 - New Extended Select commandandScrollable Reader - for review

 

I was thinking something that limited the total records that were returned; everything outside of the limit window (start record, num rows) would not be accessible via the api at all.  Additional results would require a second select.  This might be a better fit for the standard select than the scrollable reader?

 

To clarify, in SQL I would do something like this for the first page of results:

 

SELECT id, name

FROM tablename

LIMIT 0,20

 

And this for the second page:

 

SELECT id, name

FROM tablename

LIMIT 20,20

 

Etc, etc,

 

Because HTTP is stateless, there is no reason to make rows outside of the selected set available, unless there is some kind of feature cache at the FDO level that would make subsequent selects more efficient.

 

Jason

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Orest Halustchak
Sent: Monday, October 20, 2008 12:49
To: FDO Internals Mail List
Subject: RE: [fdo-internals] RFC 26 - New Extended Select commandandScrollable Reader - for review

 

Hi Jason,

 

So, this limit would be something that would return an end of fetch after reading ‘limit’ number of records? But, then you can reset it I guess when you want to get the next page (maybe just by calling ReadAtIndex() again). An issue with the scrollable reader is that you can read forwards or backwards, and jump to a new record index at any time. So, I think adding a limit would complicate this mechanism – knowing when to reset it or what it means after jumping to a new record.

 

Thanks,

Orest.

 

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Jason Birch
Sent: Monday, October 20, 2008 3:03 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] RFC 26 - New Extended Select command andScrollable Reader - for review

 

I don’t have any direct experience with this because MapGuide doesn’t currently doesn’t allow access to these commands.  I certainly see value in making these part of the common feature set though.  Maybe I’ll eventually be able to do sorting on SDF results via MapGuide J

 

One thing that occurred to me when reading this RFC was that I’d like to see a mechanism to “page” through results; similar to the LIMIT clause in MySQL.  When displaying result sets in a web environment, you often want to give the user a small set of the data, and then page through the results N records at a time.  I can currently brute-force this, but it would be more efficient to handle this on the FDO side, especially for providers where the underlying storage format has optimized methods of dealing with it.  The current enhancements would make this more efficient to brute-force, but I wonder if adding parameters to the initial selection (start record, number of results) would make this even more efficient.

 

Jason

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Orest Halustchak
Sent: Monday, October 20, 2008 11:24
To: FDO Internals Mail List
Subject: RE: [fdo-internals] RFC 26 - New Extended Select command andScrollable Reader - for review

 

Hi,

 

I wonder if anyone has any comments on this. If nobody has any objections to it, I’d like to bring it to a vote soon.

 

Thanks,

Orest.

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Orest Halustchak
Sent: Friday, October 17, 2008 12:37 PM
To: FDO Internals Mail List
Subject: [fdo-internals] RFC 26 - New Extended Select command and Scrollable Reader - for review

 

Hi,

 

I’d like to bring your attention to RFC 26 ( http://trac.osgeo.org/fdo/wiki/FDORfc26 ) which proposes to add a new Extended Select command with uses a Scrollable feature reader. Basically, this takes what currently are custom commands in the SDF, SHP, and recently SQLite providers and makes them generic FDO commands. This will remove special case handling for applications that currently use these and open the door for generic use by any application.

 

Please review and provide your feedback.

 

Thanks,

Orest.

 

_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals

[Orest Halustchak]

Some javascript/style in this post has been disabled (why?)

Hi,

 

Since I haven’t seen any objections to this change request, I’m going to ask for a vote.

 

+1 from me.

 

Thanks,

Orest.

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Orest Halustchak
Sent: Monday, October 20, 2008 2:24 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] RFC 26 - New Extended Select command and Scrollable Reader - for review

 

Hi,

 

I wonder if anyone has any comments on this. If nobody has any objections to it, I’d like to bring it to a vote soon.

 

Thanks,

Orest.

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Orest Halustchak
Sent: Friday, October 17, 2008 12:37 PM
To: FDO Internals Mail List
Subject: [fdo-internals] RFC 26 - New Extended Select command and Scrollable Reader - for review

 

Hi,

 

I’d like to bring your attention to RFC 26 ( http://trac.osgeo.org/fdo/wiki/FDORfc26 ) which proposes to add a new Extended Select command with uses a Scrollable feature reader. Basically, this takes what currently are custom commands in the SDF, SHP, and recently SQLite providers and makes them generic FDO commands. This will remove special case handling for applications that currently use these and open the door for generic use by any application.

 

Please review and provide your feedback.

 

Thanks,

Orest.

 

_______________________________________________
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?)

+1

 

Greg

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Orest Halustchak
Sent: Tuesday, October 21, 2008 4:17 PM
To: FDO Internals Mail List
Subject: [fdo-internals] Request for vote on RFC 26 - New Extended Select command and Scrollable Reader

 

Hi,

 

Since I haven’t seen any objections to this change request, I’m going to ask for a vote.

 

+1 from me.

 

Thanks,

Orest.

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Orest Halustchak
Sent: Monday, October 20, 2008 2:24 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] RFC 26 - New Extended Select command and Scrollable Reader - for review

 

Hi,

 

I wonder if anyone has any comments on this. If nobody has any objections to it, I’d like to bring it to a vote soon.

 

Thanks,

Orest.

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Orest Halustchak
Sent: Friday, October 17, 2008 12:37 PM
To: FDO Internals Mail List
Subject: [fdo-internals] RFC 26 - New Extended Select command and Scrollable Reader - for review

 

Hi,

 

I’d like to bring your attention to RFC 26 ( http://trac.osgeo.org/fdo/wiki/FDORfc26 ) which proposes to add a new Extended Select command with uses a Scrollable feature reader. Basically, this takes what currently are custom commands in the SDF, SHP, and recently SQLite providers and makes them generic FDO commands. This will remove special case handling for applications that currently use these and open the door for generic use by any application.

 

Please review and provide your feedback.

 

Thanks,

Orest.

 

_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals

[Jason Birch]

Some javascript/style in this post has been disabled (why?)

+1 Jason

 

From: Orest Halustchak
Subject: [fdo-internals] Request for vote on RFC 26 - New Extended Selectcommand and Scrollable Reader

 

Since I haven’t seen any objections to this change request, I’m going to ask for a vote.

_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals

[Orest Halustchak]

Some javascript/style in this post has been disabled (why?)

Hi,

 

It’s been almost a week from the request for vote. I haven’t seen any objections but not everyone on the PSC has voted yet.

 

Thanks,

Orest.

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Jason Birch
Sent: Wednesday, October 22, 2008 11:26 AM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] Request for vote on RFC 26 - New Extended Selectcommand and Scrollable Reader

 

+1 Jason

 

From: Orest Halustchak
Subject: [fdo-internals] Request for vote on RFC 26 - New Extended Selectcommand and Scrollable Reader

 

Since I haven’t seen any objections to this change request, I’m going to ask for a vote.

_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals

[Haris Kurtagic]

Some javascript/style in this post has been disabled (why?)

+1

Haris

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Orest Halustchak
Sent: Tuesday, October 21, 2008 10:17 PM
To: FDO Internals Mail List
Subject: [fdo-internals] Request for vote on RFC 26 - New Extended Selectcommand and Scrollable Reader

 

Hi,

 

Since I haven’t seen any objections to this change request, I’m going to ask for a vote.

 

+1 from me.

 

Thanks,

Orest.

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Orest Halustchak
Sent: Monday, October 20, 2008 2:24 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] RFC 26 - New Extended Select command and Scrollable Reader - for review

 

Hi,

 

I wonder if anyone has any comments on this. If nobody has any objections to it, I’d like to bring it to a vote soon.

 

Thanks,

Orest.

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Orest Halustchak
Sent: Friday, October 17, 2008 12:37 PM
To: FDO Internals Mail List
Subject: [fdo-internals] RFC 26 - New Extended Select command and Scrollable Reader - for review

 

Hi,

 

I’d like to bring your attention to RFC 26 ( http://trac.osgeo.org/fdo/wiki/FDORfc26 ) which proposes to add a new Extended Select command with uses a Scrollable feature reader. Basically, this takes what currently are custom commands in the SDF, SHP, and recently SQLite providers and makes them generic FDO commands. This will remove special case handling for applications that currently use these and open the door for generic use by any application.

 

Please review and provide your feedback.

 

Thanks,

Orest.

 

_______________________________________________
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?)

+1

Greg

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Haris Kurtagic
Sent: Monday, October 27, 2008 3:30 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] Request for vote on RFC 26 - New Extended Selectcommand and Scrollable Reader

 

+1

Haris

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Orest Halustchak
Sent: Tuesday, October 21, 2008 10:17 PM
To: FDO Internals Mail List
Subject: [fdo-internals] Request for vote on RFC 26 - New Extended Selectcommand and Scrollable Reader

 

Hi,

 

Since I haven’t seen any objections to this change request, I’m going to ask for a vote.

 

+1 from me.

 

Thanks,

Orest.

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Orest Halustchak
Sent: Monday, October 20, 2008 2:24 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] RFC 26 - New Extended Select command and Scrollable Reader - for review

 

Hi,

 

I wonder if anyone has any comments on this. If nobody has any objections to it, I’d like to bring it to a vote soon.

 

Thanks,

Orest.

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Orest Halustchak
Sent: Friday, October 17, 2008 12:37 PM
To: FDO Internals Mail List
Subject: [fdo-internals] RFC 26 - New Extended Select command and Scrollable Reader - for review

 

Hi,

 

I’d like to bring your attention to RFC 26 ( http://trac.osgeo.org/fdo/wiki/FDORfc26 ) which proposes to add a new Extended Select command with uses a Scrollable feature reader. Basically, this takes what currently are custom commands in the SDF, SHP, and recently SQLite providers and makes them generic FDO commands. This will remove special case handling for applications that currently use these and open the door for generic use by any application.

 

Please review and provide your feedback.

 

Thanks,

Orest.

 

_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals

[Robert Fortin]

Some javascript/style in this post has been disabled (why?)

Can we call this RFC approved?

 

Robert

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Greg Boone
Sent: Monday, November 03, 2008 2:50 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] Request for vote on RFC 26 - New Extended Selectcommand and Scrollable Reader

 

+1

Greg

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Haris Kurtagic
Sent: Monday, October 27, 2008 3:30 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] Request for vote on RFC 26 - New Extended Selectcommand and Scrollable Reader

 

+1

Haris

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Orest Halustchak
Sent: Tuesday, October 21, 2008 10:17 PM
To: FDO Internals Mail List
Subject: [fdo-internals] Request for vote on RFC 26 - New Extended Selectcommand and Scrollable Reader

 

Hi,

 

Since I haven’t seen any objections to this change request, I’m going to ask for a vote.

 

+1 from me.

 

Thanks,

Orest.

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Orest Halustchak
Sent: Monday, October 20, 2008 2:24 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] RFC 26 - New Extended Select command and Scrollable Reader - for review

 

Hi,

 

I wonder if anyone has any comments on this. If nobody has any objections to it, I’d like to bring it to a vote soon.

 

Thanks,

Orest.

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Orest Halustchak
Sent: Friday, October 17, 2008 12:37 PM
To: FDO Internals Mail List
Subject: [fdo-internals] RFC 26 - New Extended Select command and Scrollable Reader - for review

 

Hi,

 

I’d like to bring your attention to RFC 26 ( http://trac.osgeo.org/fdo/wiki/FDORfc26 ) which proposes to add a new Extended Select command with uses a Scrollable feature reader. Basically, this takes what currently are custom commands in the SDF, SHP, and recently SQLite providers and makes them generic FDO commands. This will remove special case handling for applications that currently use these and open the door for generic use by any application.

 

Please review and provide your feedback.

 

Thanks,

Orest.

 

_______________________________________________
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.

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Robert Fortin
Sent: Wednesday, November 05, 2008 11:09 AM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] Request for vote on RFC 26 - New Extended Selectcommand and Scrollable Reader

 

Can we call this RFC approved?

 

Robert

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Greg Boone
Sent: Monday, November 03, 2008 2:50 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] Request for vote on RFC 26 - New Extended Selectcommand and Scrollable Reader

 

+1

Greg

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Haris Kurtagic
Sent: Monday, October 27, 2008 3:30 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] Request for vote on RFC 26 - New Extended Selectcommand and Scrollable Reader

 

+1

Haris

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Orest Halustchak
Sent: Tuesday, October 21, 2008 10:17 PM
To: FDO Internals Mail List
Subject: [fdo-internals] Request for vote on RFC 26 - New Extended Selectcommand and Scrollable Reader

 

Hi,

 

Since I haven’t seen any objections to this change request, I’m going to ask for a vote.

 

+1 from me.

 

Thanks,

Orest.

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Orest Halustchak
Sent: Monday, October 20, 2008 2:24 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] RFC 26 - New Extended Select command and Scrollable Reader - for review

 

Hi,

 

I wonder if anyone has any comments on this. If nobody has any objections to it, I’d like to bring it to a vote soon.

 

Thanks,

Orest.

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Orest Halustchak
Sent: Friday, October 17, 2008 12:37 PM
To: FDO Internals Mail List
Subject: [fdo-internals] RFC 26 - New Extended Select command and Scrollable Reader - for review

 

Hi,

 

I’d like to bring your attention to RFC 26 ( http://trac.osgeo.org/fdo/wiki/FDORfc26 ) which proposes to add a new Extended Select command with uses a Scrollable feature reader. Basically, this takes what currently are custom commands in the SDF, SHP, and recently SQLite providers and makes them generic FDO commands. This will remove special case handling for applications that currently use these and open the door for generic use by any application.

 

Please review and provide your feedback.

 

Thanks,

Orest.

 

_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals

[W Khattak]

Hi,

Just wanted to ask if there is any chance of getting a reader with the "Page Size " property (as described by Jason) in 3.4.0?

regards,

W Khattak

[Greg Boone]

No.. I doubt we would be able to do this for 3.4.0. It would have to be proposed again for 3.5.

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of W Khattak
Sent: Tuesday, February 10, 2009 7:41 AM
To: [hidden email]
Subject: RE: [fdo-internals] RFC 26 - New Extended Select commandandScrollable Reader - for review


Hi,

Just wanted to ask if there is any chance of getting a reader with the "Page
Size " property (as described by Jason) in 3.4.0?

regards,

W Khattak
--
View this message in context: http://n2.nabble.com/RFC-26---New-Extended-Select-command-and-Scrollable-Reader---for-review-tp2051824p2302307.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

[W Khattak]

Hi Jason,

I just wanted to ask that what sort of technique are you using for getting a subset of features from MG for a particular search? The problem is that the kind of data I am working with contains huge amounts of features per data source and I have a search page where the results are shown in a paged Grid View. Initially I thought about caching the results in SQl Server whereby when the user performs the search for the very first time , the attributes of the features are put into a table & then using custom paging, getting only 10 rows while the user is paging through the results and to re-insert new rows when the user changes the search criteria. Clearly this doesn't sound good as there is no way of checking if the cache is invalid or not unitl and unless you query MG again. I have thought about a few ways but cann't really think of a good solution for caching MG's results or alternatively getting only a subset of features from MG.

regards,

W Khattak

Jason Birch wrote:

I don't have any direct experience with this because MapGuide doesn't
currently doesn't allow access to these commands.  I certainly see value
in making these part of the common feature set though.  Maybe I'll
eventually be able to do sorting on SDF results via MapGuide J

 

One thing that occurred to me when reading this RFC was that I'd like to
see a mechanism to "page" through results; similar to the LIMIT clause
in MySQL.  When displaying result sets in a web environment, you often
want to give the user a small set of the data, and then page through the
results N records at a time.  I can currently brute-force this, but it
would be more efficient to handle this on the FDO side, especially for
providers where the underlying storage format has optimized methods of
dealing with it.  The current enhancements would make this more
efficient to brute-force, but I wonder if adding parameters to the
initial selection (start record, number of results) would make this even
more efficient.

 

Jason

 

From: [e-mail]
[mailto:[e-mail]] On Behalf Of Orest
Halustchak
Sent: Monday, October 20, 2008 11:24
To: FDO Internals Mail List
Subject: RE: [fdo-internals] RFC 26 - New Extended Select command
andScrollable Reader - for review

 

Hi,

 

I wonder if anyone has any comments on this. If nobody has any
objections to it, I'd like to bring it to a vote soon.

 

Thanks,

Orest.

 

From: [e-mail]
[mailto:[e-mail]] On Behalf Of Orest
Halustchak
Sent: Friday, October 17, 2008 12:37 PM
To: FDO Internals Mail List
Subject: [fdo-internals] RFC 26 - New Extended Select command and
Scrollable Reader - for review

 

Hi,

 

I'd like to bring your attention to RFC 26 (
http://trac.osgeo.org/fdo/wiki/FDORfc26 ) which proposes to add a new
Extended Select command with uses a Scrollable feature reader.
Basically, this takes what currently are custom commands in the SDF,
SHP, and recently SQLite providers and makes them generic FDO commands.
This will remove special case handling for applications that currently
use these and open the door for generic use by any application.

 

Please review and provide your feedback.

 

Thanks,

Orest.

 


_______________________________________________
fdo-internals mailing list
[e-mail]
http://lists.osgeo.org/mailman/listinfo/fdo-internals