Explicit change tracking required for the array field...

[tmlipinski]

Hi,
I get this warning for array, binary columns (MS SQL: binary, varbinary(n) and varbinary(max)). As I understand, it means that without some additional code changes in such columns will not be saved. Am I right and what code should be added?

Regards
Tomasz

[Dimitar Kapitanov]

Hi tmlipinski,
OpenAccess is unable to determine changes inside an array representation. That's why the best approach to modify such a property is through a method on the enhanced class, and have there additional logic to accomplish the update successfully.

Greetings,
Dimitar Kapitanov
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.

[tmlipinski]

Hi,
Could you, please, refer me to a documentation topic or a code example?
Regards
Tomasz

[Dimitar Kapitanov]

Hi tmlipinski,
This topic is marked for documentation. When we have it we will make it publicly available.

Kind regards,
Dimitar Kapitanov
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.

[Greg]

Any update regarding documentation or examples for this issue?  With the inclusion of the new Column types in Radgrid, it would be helpful to see how to deal with this issue, or documentation regarding it for the ORM.  I have tables with image datatypes, and without getting into the philosophical debate on whether images or binary data should be stored in the database, the bottom line is, we are, so further information on the topic would be great.

Thanks as always,
Kuba 

[Alexander]

Hi Kuba Cole,

Unfortunately we do not have documentation on this topic yet. However, I will try to shed some light here. The meaning of this warning is the following - If you have an array field in some persistent class and change the whole array with another, change tracking will work, but if you change only one element of the array, it will not. So, to avoid this behavior, the field should be explicitly marked as "Dirty" when such operation occurs. You can use the ObjectScope.MakeDirty(object, fieldName) method to do this when necessary. Hope that helps.

Greetings,
Alexander
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.

[hkdave95]

Hi

I have the same warnings.

Please let me know when this documentation is ready.

Thank you

David

[Alexander]

Hi David,

Sure, we will do so. Most probably the topic will be available for the next release.

Kind regards,
Alexander
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

[Alexander]

Hi David,

The article on this topic is ready and published in our Knowledge Base section. It will be available in the product documentation as well with the upcoming 2009 Q3 release.

Kind regards,
Alexander
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.