Hi Pearl guys,
I need your help (please) with the next part of my L2S (LINQ to SQL) development.
It would appear that the query syntax for LINQ requires me to use SQL style query syntax and does not allow me to use .NET stuff in the LINQ query itself.
I have attached a few small images to show you my problem. I have a column type of 'smallmoney' which in .NET maps to a Decimal type. If I want to compare with a double 'cash' value type then I hit my problems.
Oh! and to cap it all off the .NET type is a Nullable<Decimal> needed to map to the defined SQL table column, which can be null.
HELP !! help ?? HELP !?
Nick, where are those SQL skills of yours ;-0)
Regards,
Phil.
LINQ to SQL - some advice on Decimal types !?
- Phil Hepburn
- Posts: 743
- Joined: Sun Sep 11, 2016 2:16 pm
LINQ to SQL - some advice on Decimal types !?
Phil,
Change the literal value to 26.13m (m = money) and it will probably compile fine.
Robert
Change the literal value to 26.13m (m = money) and it will probably compile fine.
Robert
XSharp Development Team
The Netherlands
robert@xsharp.eu
The Netherlands
robert@xsharp.eu
- Phil Hepburn
- Posts: 743
- Joined: Sun Sep 11, 2016 2:16 pm
LINQ to SQL - some advice on Decimal types !?
Hi Robert,
Yes, many thanks, it now all works well, and I have learned a few useful things on the way to enlightenment ;-0) Like what can and can't be placed in the query code of the LINQ statement.
In fact I had discovered the 'M' myself, but had not applied it directly as you suggested I should. Then BINGO ! Success.
A couple of useful and informative attachments for those guys interested. Note the method is one defined in the 'DataContext' class - which is the class of object which sits between the SQL Tables and the .NET business class objects - like a 'bridge' it does the mapping, along with the Attributes on the business class.
Thanks again,
Phil.
Yes, many thanks, it now all works well, and I have learned a few useful things on the way to enlightenment ;-0) Like what can and can't be placed in the query code of the LINQ statement.
In fact I had discovered the 'M' myself, but had not applied it directly as you suggested I should. Then BINGO ! Success.
A couple of useful and informative attachments for those guys interested. Note the method is one defined in the 'DataContext' class - which is the class of object which sits between the SQL Tables and the .NET business class objects - like a 'bridge' it does the mapping, along with the Attributes on the business class.
Thanks again,
Phil.