Loïc LEFEVRE

Results 20 comments of Loïc LEFEVRE

You didn't initialize the Visual Studio environnement variables. Check Windows prerequisites https://www.graalvm.org/22.0/reference-manual/native-image/#prerequisites And in the linked medium blog post, don't forget the step: C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Auxiliary\Build\vcvars64.bat

> This looks like a rather dangerous change to me. There are numerous examples of projects which simply break when things are added on the module path. Also this changes...

Ok, I've added a new plugin parameter: `inferModulePath` ```xml org.graalvm.buildtools native-maven-plugin ${native.maven.plugin.version} build-native compile-no-fork package test-native test test true false ${imageName} false false true --module-path target/connectme-1.0.0.jar -Ob -march=native --initialize-at-build-time=com.oracle.connect/com.oracle.connect.Main --add-modules...

Sorry to say that's not solving the issue. Thanks

@lukasj, there is also `CREATE SEARCH INDEX ...` for Oracle DB: See [JSON Developer Guide](https://docs.oracle.com/en/database/oracle/oracle-database/23/adjsn/indexes-for-json-data.html#GUID-D7A604E1-F617-4C92-A9D9-00B6AB78EFD8) See [XML Developer Guide](https://docs.oracle.com/en/database/oracle/oracle-database/23/adxdb/indexes-for-XMLType-data.html#GUID-6ED52730-5C05-4432-A8A3-6F470D067C43)

The `type` for `@Index` looks exactly like what we need. This is also needed for `@Table`; I'm not sure about the others though. I also wanted to double-check if the...

I can see 3 types of index where validating the grammar could be problematic: - function based indexes - JSON Path expressions to be indexed (a special case for first...