REST API > POST COMMAND > COMMAND TEXT > FETCHPLAN in SELECT command not working

[octal-laurence]

OrientDB Version:

Java Version:

OS:

Expected behavior

the field applicant should expand as I use fetching strategies

Actual behavior

"result": [
{
"applicant": [
"#14:171"
],
"address": [
"#13:167"
],
"machineId": "DDDDD",
"dateCreated": "2018-12-13 12:02:12",
"purpose": ".",
"in_certificationApplicants": [
"#15:155"
],
"station": "DDDDD",
"stationName": "DDDDD",
"remarks": "",
"dateUpdated": "2018-12-13 12:02:12",
"status": "OPEN",
"@Rid": "#12:174",
"@Version": 1,
"@Class": "policeClearanceCertifications"
}
],

Steps to reproduce

My code is

return rp.post('http://localhost/command/database/sql', {
command: SELECT IN('${this._edgePoliceClearanceCertifications.tbl}') as applicant, IN('${this._edgePoliceClearanceCertifications.tbl}').IN('${this._edgeApplicantsAddress.tbl}') as address, * FROM ${rid} fetchplan *:1
});

[luigidellaquila]

Hi @octal-laurence

Which version are you using? If it's v 3.0, I strongly suggest you to use nested projections instead https://orientdb.com/docs/3.0.x/sql/SQL-Projections.html#nested-projections (fetch plans are deprecated)

Thanks

Luigi

[octal-laurence]

Hi @octal-laurence

Which version are you using? If it's v 3.0, I strongly suggest you to use nested projections instead https://orientdb.com/docs/3.0.x/sql/SQL-Projections.html#nested-projections (fetch plans are deprecated)

Thanks

Luigi

I'd check on it just now.

Hi, thanks for the assistance, May I ask is this solution can be use also in querying the edges? like in my given example query.

also I used some other methods too, like IN("edges query").toJson() seems fine, just checking if those are accurate