This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I'm using Lightspeed 4.0524.17831, but I've tried with the last nightly release and the results are the same. We have a base class called Product, and a sub class called SpecialOfferProduct. There are concrete instances of both classes. We have the Discriminator attribute only on SpecialOfferProduct. SpecialOfferProduct has fields that are not on Product. When retrieving instances of Product, everything works as expected (i.e. the STI works and the fields are populated), except if we retrieve Product via a ProcedureQuery, or via a LINQ join. In this case, the extra fields on SpecialOfferProduct are not populated correctly, even though the type of the object is set up as expected. For example, we have also have a PrinterProduct entity, that has ProductId and PrinterId fields. When trying to retrieve all the products for a given Printer:
Any Products that are SpecialOfferProducts, are returned with the correct type, but are not correctly initialised. I got the same behaviour when calling a stored procedure via a ProcedureQuery. I've successfully split the query into two parts:
And in this case, the fields on SpecialOfferProduct are initialised as expected. Any idea what is going on here? Thanks in advance Henry |
|
|
Hi Henry, Thanks for reporting this. This is a bug and I have repro'ed the behavior here. I will get a fix into a nightly build for you shortly and post an update once this is available for you to download.
|
|
|
Hi Henry, Just an update to let you know that a fix for this will be available for you in the next nightly build.
|
|
|
Thanks Jeremy, I've just tested with the nightly build and can confirm that the issue is fixed. Any idea when is the next scheduled proper formal release? Or are the nightly builds fully tested and good to go? Cheers Henry |
|
|
Hi Henry, Nightly builds only go through our usual unit tests (of which there is ~23,000 of them) but they don't go through the same level of testing as a formal release (for obvious time consuming reasons!). The next formal release will be LightSpeed 5 which we are aiming to have completed within the next few months.
|
|