[fdo-internals] IInsert.BatchParameterValues problems

[Maksim Sestic]

Hi Greg,

It's Autodesk.SqlServer provider.

Regards,
Maksim Sestic


gregboone wrote:
> 
> Which provider(s)? SDF?
> 
> -----Original Message-----
> From: fdo-internals-bounces at lists.osgeo.org
> [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Maksim Sestic
> Sent: Wednesday, March 05, 2008 10:27 AM
> To: fdo-internals at lists.osgeo.org
> Subject: RE: [fdo-internals] IInsert.BatchParameterValues problems
> 
> 
> Hi Greg,
> 
> I'm currently maintaining a code that does consecutive
> IInsert.PropertyValues.Add(...) followed by IInsert.Execute to fill the
> database row-by-row. I don't have working example of BatchParameterValues.
> 
> So, once managed IInsert object gets instantiated, it's properties (of
> interest) reflect the following:
> 
> - PropertyValues As PropertyValueCollection (ReadOnly) - an empty
> collection
> - ParameterValues As ParameterValueCollection (ReadOnly) - Nothing/Null
> (!)
> - BatchParameterValues As BatchParameterValueCollection (ReadOnly) -
> Nothing/Null (!)
> 
> If I understood Orest correctly, if provider supported parameters in first
> place - both ParameterValues and BatchParameterValues properties should
> reflect empty collections after IInsert was instantiated (?)... But these
> collections should be available (already instantiated) neverthless, since
> IInsert.Execute would throw an error if parameters capability wasn't
> supported by provider. Or I simply misunderstood Orest and this is a bug
> in
> managed wrapper :-)
> 
> Regards,
> Maksim Sestic
> 
> 
> 
> gregboone wrote:
>>
>> So you have managed code available that illustrates?
>>
>> -----Original Message-----
>> From: fdo-internals-bounces at lists.osgeo.org
>> [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Maksim Sestic
>> Sent: Wednesday, March 05, 2008 6:16 AM
>> To: fdo-internals at lists.osgeo.org
>> Subject: RE: [fdo-internals] IInsert.BatchParameterValues problems
>>
>>
>> Hi Orest,
>>
>> If I understood well - in case provider does support parameters, managed
>> IInsert will get instantied with BatchParameterValues propery containing
>> empty BatchParameterValuesCollection collection. Otherwise - the property
>> is
>> Nothing (Null)... Something's strange here, the collection should exist
>> in
>> first place neverthless of provider's capabilities (it should throw an
>> error
>> afterwards, on IInsert.Execute).
>>
>> Is this an error in managed wrapper or a feature? :-)
>>
>> Regards,
>> Maksim Sestic
>>
> 
> --
> View this message in context:
> http://www.nabble.com/IInsert.BatchParameterValues-problems-tp15824346s18162p15852596.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://www.nabble.com/IInsert.BatchParameterValues-problems-tp15824346s18162p15868283.html
Sent from the fdo-internals mailing list archive at Nabble.com.