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
|
Hi, We've upgraded to Lightspeed 5 recently and it appears to be causing an issue whenever we need to do a query on concatenated string values for example:
var query =
from e in sqlUow.Query will generate a sql query containing a || (instead of a '+') for the concatenation eventhough we're using SQL Server. It this is known issue and if so, is there a workaround for this? If not, would you be able to fix this? Thanks! |
|
|
Are you able to send through a small repro project for this which we can have a look at? The SQL Server providers should be using + to concatenate strings and this is the case in our test cases here.
|
|
|
Try this - run the test in lightspeedtest. Thanks |
|
|
Hi Jeremy, Any news on this one? John |
|
|
Thanks for the repro project. This was an issue when using the SQL 2012 provider on the RTM build of 5.0. You will need to grab a current nightly build to resolve this as this has actually already been fixed by an update from a week or two back which corrected a couple of missing checks for the SQL 2012 provider to apply custom behavior such as this.
|
|
|
Fixing bugs before they are logged, no wonder they say your support is good :-) Can you give us any advice on how to choose which nightly build to use? E.g. are they all equally stable, or are some nightlies more trustworthy (for production use) than others? Does a 5.0 nightly build include just bug-fixes to 5.0, or does it also tend to include brand new stuff that might pose stability risks? I'm sure you have plans and processes in this regard, but if they are already documented on the Mindscape site I haven't found them yet... |
|
|
The nightlies could contain both, but it will primarily just be bug fixes (and currently that is indeed the case). As a "general rule" now we are looking to push out more regular minor version releases to include requested features and provider updates and keep the nightlies as more strictly bug fixes to provide a bit more confidence in using the nightlies for this reason. They are all equally stable in terms of test coverage and the like. Some other info which is relevant would be to point out that for any "breaking" changes which come about from bug fixes we keep these off by default by using the Compatibility Options on the context to control when these are applied.
|
|
|
Fantastic thanks Jeremy. The new "general rule" sounds nice. Regards, John |
|