Depending on what happens with this PR #30010. I might continue with adding those as well...

Hi @roji as I see @joelmandell PR is stuck. I'd like to try to implement this by:

1. Create JsonExists in RelationalDbFunctionsExtensions that throws an exception
2. Create SqlServerJsonExistTranslator
3. Create SqliteJsonExistTranslator
4. Register translators at SqlServerMethodCallTranslatorProvider and SqlliteMethodCallTranslatorProvider accordingly
   I believe that will support JSON PATH for SQL Server and SQLite providers, but will throw an exception for any other relational provider unless their developers implement support for one.
   Can I do it?

@abcdefgabcefg I am just waiting for feedback on that PR before I started on the other things. That's why I am lagging behind

@joelmandell oh sorry, I don't I was aware you were waiting for feedback there... we've unfortunately gone into feature freeze for 8.0 so we won't be able to merge it for that...

@roji please tell, this issue is also frozen till EF 8?

EF 8 will be out in November, and feature work on it has stopped; we're now stabilizing/fixing bugs only. Any feature PR will generally be merged for EF 9 at this point, which will come out in November 2024.

Hi @roji , is this issue still open for contribution?

@Ricketiman and others, @joelmandell made good progress on this in #30010 - it's my fault it hasn't progressed. I'm generally trying to make progress on dormant PRs, I'll try to pick up this work again - I don't think it makes sense to start a new PR.

Hi @roji , Is this Issue still open for contribution?

Yes.

Hi @roji , I would like to try working on this issue if it's open for contribution
what is the status of this PR #30010? I think it would be better if the common json functions added on the relational level as well not just JsonExists

what is the status of this PR #30010?

We're unfortunately backed up on processing community PRs; #30010 looks like it's in the right direction but we need to find some time to get it to mergeable state.

I think it would be better if the common json functions added on the relational level as well not just JsonExists

It's a good idea to do this method by method, since support across databases varies in this area. Definitely feel free to open more issues like this one, detailing the proposed translations across databases (see the origina post above).

@roji I will start working on JsonExists for now and after that creating issue with other function proposals and work on them one by one.

I will use case expression or iif for sqlite to maintain the same behavior as follow

CASE 
    WHEN [json_value] IS NULL THEN NULL
    ELSE json_type([json_value], [json_path]) IS NOT NULL
END

iif([json_value] IS NULL, NULL, json_type([json_value], [json_path]) IS NOT NULL)