Thanks! We will add a test for this.

Can I take this up as discussed in Discord? Here's how I am looking to do this.

Step 1: Write a test in db_test.go for fetch to ensure fetch works properly.
Step 2: Replicate this particular error in the test case to see if it's currently working
Step 3: Based on Step 2, decide if we need a fix or this is already done and push the test case for fetch as it is.

Yes please @sbshah97 ! That is exactly what is needed

Hi had some work, picking this back up

Sorry for delay here to way to reproduce

func (s *SurrealDBTestSuite) TestFetch() {
	userSlice := []testUser{
		{Username: "arthur", Personal: PersonalInfo{Name: "arthur", Surname: "morgan"}, Password: "deer", Friends: []string{"users:john"}},
	}

	for _, v := range userSlice {
		data, err := s.db.Create(v.ID, v)
		s.NoError(err)
		s.NotNil(data)
	}

	for _, v := range userSlice {
		res, err := s.db.Query("select * from $table fetch $fetchstr;", map[string]interface{}{
			"record":   v.ID,
			"fetchstr": "friends.*",
		})
		// it will throw err
		fmt.Println(res, err)
		s.NoError(err)
		s.NotNil(res)
	}
}

ElecTwix@6af3184#diff-842765a20a0a937a8eb5267b53fb11b7493cc6c2a6a8871e1da2b684702c5bc9R502

db_test.go:503: 
Error Trace:	/home/electwix/dev/go/surrealdb.go/db_test.go:503
Error:      	Received unexpected error:
sending request failed for method 'query': There was a problem with the database: Parse error: Failed to parse query at line 1 column 28 expected a idiom
1 | select * from $table fetch $fetchstr;
Test:       	TestSurrealDBSuite/gorilla/TestFetch

to reproduce

just clone the repo and run go test -v

What is v.ID over here?

What is v.ID over here?

came from testUser's ID on db_test.go

Update: It was my bad updated commit with ElecTwix@fde06eb

From the looks of it issue here seems to be not being able to parse the fetch string. Just want to confirm if we are seeing this in other drivers or not ?

cc: @timpratim @phughk ?

If not probably will dive again in on this but from what I could see adding fmt statements till the end of the call stack, the query is being sent as correctly as possible.

After reproducing the issue with SurrealQL,
I created an issue on the SurrealDB repo: surrealdb/surrealdb#3028

Thanks @ElecTwix and @sbshah97 !