[fdo-internals] New RFC 30 Posted

[Haris Kurtagic]

Yes I understood that. I am afraid that it can be dangerous to use
readers as input to another command.

One of thing would be that reader would not be closed before another
command would be executed.

Not necessarily but I am worried that it could create problems with
current readers/commands.

 

If we look further as you suggested to improve performance of readers,
than it would be better to have them to returned shared pointers to data
or to be able to set data buffers to be used by readers.

But even before that I would prefer to have index access to columns of
readers as we speak of performance, we discussed it few times :)

 

Haris

 

From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Traian
Stanev
Sent: Monday, November 24, 2008 8:41 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] New RFC 30 Posted

 

 

Yes, but creating PropertyValues would be a performance overhead. That's
why I'm suggesting the alternative approach of allowing commands to pull
the feature's data directly from a FeatureReader (or equivalent).

 

Traian

 

From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Haris
Kurtagic
Sent: Monday, November 24, 2008 2:25 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] New RFC 30 Posted

 

 

Right now from Reader we can't get PropertyValues only raw data.

To get Property value and property value collection which then could be
passed to another command would be of great help and remove some of
unnecessary  data conversions.

 

Haris

 

From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Traian
Stanev
Sent: Monday, November 24, 2008 7:39 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] New RFC 30 Posted

 

 

 

An alternative to this suggestion is to make the destination command
accept an FdoIFeatureReader (or something equivalent that provides
access to property values in a procedural way) as argument, rather than
a collection of PropertyValues. I was thinking of this when I was
implementing the SDF->SQLite converter, which requires two translations
from PropertyValue to raw data - once when initializing the inputs of
the insert command and a second time inside the destination provider
when matching the input property values to the destination schema.

 

Traian

 

 

 

From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Haris
Kurtagic
Sent: Monday, November 24, 2008 8:27 AM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] New RFC 30 Posted

 

Hi Brent,

not directly related to this RFC but still it is important issue
regarding FDO data values.

 

I find a problem working with FDO Readers and commands is that I need to
get value as basic type from reader and then convert to FdoDataValue
etc...

I would like to be able to use data values and properties with values
from readers directly and make those as input value for another FDO
command.

Right now I need to check data type returned from property get that data
as native convert back to fdo data value and put as input to FDO
command.

 

Haris

 

From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Brent
Robinson
Sent: Friday, November 21, 2008 7:32 PM
To: FDO Internals Mail List
Subject: [fdo-internals] New RFC 30 Posted

 

Hi,

 

RFC 30 (http://trac.osgeo.org/fdo/wiki/FDORfc30) is now ready for
review. The main purpose is add FDO API functions to encapsulate
conversions between different FDO data types. Please review and let me
know if you have any questions or comments.

 

If approved, this one will likely be implemented 2 versions after FDO
3.3. 

 

Thanks,

Brent.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/fdo-internals/attachments/20081124/747f9483/attachment.html