.netcore 2.0 'ORA-00920: invalid relational operator'

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for Oracle
Velu
Posts: 20
Joined: Wed 02 Aug 2017 14:01

.netcore 2.0 'ORA-00920: invalid relational operator'

Post by Velu » Wed 29 Nov 2017 10:09

HI,



We are using .netcore 2.0,
Aspnetzero V5
Entity framework Code First.
Devart.Data.Oracle.EFCore 9.5.399

While updating the database, We have some errors.
Error Description:
'ORA-00920: invalid relational operator'

Please helps us to resolve this.

Thanks

Shalex
Site Admin
Posts: 9543
Joined: Thu 14 Aug 2008 12:44

Re: .netcore 2.0 'ORA-00920: invalid relational operator'

Post by Shalex » Wed 29 Nov 2017 13:14

The bug with using bool properties in the Where() clause of LINQ query in EF Core 2 is fixed. We will notify you when the corresponding public build is available.

If that is not the case, please contact us and attach a small test project for reproducing the issue.

Velu
Posts: 20
Joined: Wed 02 Aug 2017 14:01

Re: .netcore 2.0 'ORA-00920: invalid relational operator'

Post by Velu » Thu 30 Nov 2017 11:43

HI,

Thanks, But its urgent and needful.

Can you send me a prerelease?

Thanks.

Shalex
Site Admin
Posts: 9543
Joined: Thu 14 Aug 2008 12:44

Re: .netcore 2.0 'ORA-00920: invalid relational operator'

Post by Shalex » Thu 30 Nov 2017 17:12

We have sent you the NuGet packages with the fix.

Velu
Posts: 20
Joined: Wed 02 Aug 2017 14:01

Re: .netcore 2.0 'ORA-00920: invalid relational operator'

Post by Velu » Thu 30 Nov 2017 23:55

We have not got any email. Can you please help us in getting this.

Velu
Posts: 20
Joined: Wed 02 Aug 2017 14:01

Re: .netcore 2.0 'ORA-00920: invalid relational operator'

Post by Velu » Fri 01 Dec 2017 08:14

Hi,

We have got the mail.

The current problem (bool properties in the Where()) have got solved.

But, We have got another error and raised ticket for this(ticket ID: 239422).

Please help us to solve this issue.

Thanks.

Velu
Posts: 20
Joined: Wed 02 Aug 2017 14:01

Re: .netcore 2.0 'ORA-00920: invalid relational operator'

Post by Velu » Mon 04 Dec 2017 11:27

HI,

Please help us to resolve this issue,
We are waiting for your response.

Thanks

Shalex
Site Admin
Posts: 9543
Joined: Thu 14 Aug 2008 12:44

Re: .netcore 2.0 'ORA-00920: invalid relational operator'

Post by Shalex » Mon 04 Dec 2017 17:37

Velu wrote:We have got another error and raised ticket for this(ticket ID: 239422).
Thank you for your report. We will answer you in the ticket 239422.

Velu
Posts: 20
Joined: Wed 02 Aug 2017 14:01

Re: .netcore 2.0 'ORA-00920: invalid relational operator'

Post by Velu » Thu 07 Dec 2017 07:15

Hi,

Please check thicket, We are waiting for your reply.

Its very urgent,

Request you to solve this problem...

Thanks

Shalex
Site Admin
Posts: 9543
Joined: Thu 14 Aug 2008 12:44

Re: .netcore 2.0 'ORA-00920: invalid relational operator'

Post by Shalex » Thu 07 Dec 2017 19:28

We are processing your request. We will notify you about the results as soon as any are available.

Velu
Posts: 20
Joined: Wed 02 Aug 2017 14:01

Re: .netcore 2.0 'ORA-00920: invalid relational operator'

Post by Velu » Sun 10 Dec 2017 02:07

Any luck in this problem. Please help us in this.

Velu
Posts: 20
Joined: Wed 02 Aug 2017 14:01

Re: .netcore 2.0 'ORA-00920: invalid relational operator'

Post by Velu » Tue 12 Dec 2017 01:27

Please help us in this problem. We are waiting for your reply.

Shalex
Site Admin
Posts: 9543
Joined: Thu 14 Aug 2008 12:44

Re: .netcore 2.0 'ORA-00920: invalid relational operator'

Post by Shalex » Tue 12 Dec 2017 14:47

The investigation is in progress. As soon as we have any results, we will contact you.

Velu
Posts: 20
Joined: Wed 02 Aug 2017 14:01

Re: .netcore 2.0 'ORA-00920: invalid relational operator'

Post by Velu » Sat 16 Dec 2017 02:57

Any luck in identifying the problem. We are waiting for your reply. Please help us in this.

Shalex
Site Admin
Posts: 9543
Joined: Thu 14 Aug 2008 12:44

Re: .netcore 2.0 'ORA-00920: invalid relational operator'

Post by Shalex » Mon 18 Dec 2017 16:35

The issue is fixed. We will send you the internal build by email soon.

Post Reply