Richard Jebb wrote:
We have just hit a problem in the porting of our application to Cache, namely that if you define a property as an array collection you get a <MAXSTRING> error when you try to persist the object if the array contains a lot of data. In our case, we need to save 2000 data points, represented as %Floats.
ISC support have confirmed this as a problem and suggested we work around it by using parent/child relationships instead. Unfortunately the performance of these (as of 5.0.7) is dismal. As a further refinement, they have now suggested simply writing the data directly into the global representing the class data. In principle, this is OK (as we don't need to expose the values via SQL, and we have specific accessor methods for all our properties anyway), and the performance is terrific.
However, there is almost no information that I can find on the do's and don'ts of mixing home grown global nodes into the stuff generated by Studio. Is anyone aware of any "howto" documentation for people who want to start tweaking storage definitions? Also, if I did want to subsequently expose this sort of data via SQL, how would I go about building the mappings?
All suggestions welcome!
Richard
