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
|
We have a table like this: CREATE TABLE IPS_JOURNALS Lightspeed generator created the following (excerpt): <entity name="Journal" identityType="Int32" cacheExpiry="0" tableName="IPS_JOURNALS"> < entityProperties><entityProperty name="Worker">< validations><presenceValidation />< lengthValidation minimumLength="0" maximumLength="50" /></validations></ entityProperty><entityProperty name="ActualWork" dataType="Decimal" isNullable="true" columnName="ACTUAL_WORK" />< entityProperty name="WorkDay" dataType="DateTime" isNullable="true" columnName="WORK_DAY" /><entityProperty name="Category" isNullable="true">< validations><lengthValidation minimumLength="0" maximumLength="1" /></ validations></entityProperty>< entityProperty name="Remark" isNullable="true"><validations>< lengthValidation minimumLength="0" maximumLength="200" /></validations></ entityProperty><entityProperty name="DateEntered" dataType="DateTime" isNullable="true" columnName="DATE_ENTERED" /></ entityProperties></ entity>
Anyway, when I try to load the data from the database, I get a blank ActualWork property. All other properties are correctly loaded. |
|
|
Hello milivojm, This looks like an issue between LightSpeed and the Oracle ODP.NET provider. Can you confirm that you are using Oracle9Odp rather than Oracle9? I will investigate this and aim to get you a fix shortly; in the meantime you can work around it by using the Oracle9 provider (I know this is slower, but it doesn't seem to exhibit the same problem, and will hopefully allow you to continue working while we sort out the ODP.NET issue). |
|
|
Another workaround is to change the data type of ActualWork from Decimal to Single. |
|
|
Okay, this is now fixed and the fix will be included in nightly builds dated 22 Nov 2008 and above, available from http://www.mindscape.co.nz/products/lightspeed/nightlybuilds.aspx or from the store after about 1430 GMT. The issue was that Oracle ODP.NET was returning a float value for ACTUAL_WORK, and converting this to a nullable decimal was resulting in null. I have adjusted the conversion behaviour so that the float value will now be correctly converted to a decimal. Please let us know if you still see problems after installing the nightly build. Thanks! |
|
|
Hi, thank you for your quick reply. Workaround accepted and working. Single workaround works fine. Using Oracle9 provider also works fine. What is the cause of speed issue between Oracle9 and Oracle9ODP providers? Is it Oracle related or ? I downloaded the latest build but it is still not the one dated 22 Nov, it's 21 Nov, product version 2.1.819.9740. I will post here after the build is released. Thanks.
|
|
|
"What is the cause of speed issue between Oracle9 and Oracle9ODP providers? Is it Oracle related or ?" It's Oracle related. The Oracle9 provider uses the built-in, Microsoft-provided Oracle client library (System.Data.OracleClient). The Oracle9Odp provider uses Oracle's own ODP.NET library (Oracle.DataAccess.dll), which we understand is quite a bit faster, but requires additional deployment. |
|