Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Cannot use SQL method with WHERE something > number

Open
#17 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
api

Research direction

Start with the SQLRequest type and the lightning.Request call shown in the issue, then reproduce the failure using the linked test repository. Trace JSON encoding around Request and compare it with the working shell JSON-RPC request; done means a query containing WHERE expiry > 1 succeeds without the unrecognized-token error.

Written by the indexing model from the issue text.

Description

This query works using lighting-cli:

$ lightning-cli sql -k query="SELECT * FROM htlcs WHERE expiry > 1;"
{
   "rows": [
      [
         2381,

It also works using JSON-RPC in shell:

$ echo '{"method": "sql", "params": {"query": "SELECT * FROM htlcs WHERE expiry > 1;"}, "id": 1, "jsonrpc": "2.0"}' | nc -U ${PWD}/.lightning/testnet/lightning-rpc
{"jsonrpc":"2.0","id":1,"result":{"rows":[[2456,"2821409x111x0",0,2821429,1000000,"in","c95ad151010e9cc14238bce909e6e8545258fc07d0e00c98a4b5ff90ac049e61","SENT_REMOVE_ACK_REVOCATION"],[2457,"2821

But it DOES NOT work with glightning:

type SQLRequest struct {
	Query string `json:"query"`
}

func (r SQLRequest) Name() string {
	return "sql"
}
....
// this fails with error
// -1:query failed with unrecognized token: "\"
err = lightning.Request(&SQLRequest{
Query: "SELECT * FROM htlcs WHERE expiry > 1;",
}, &response)

glightning is apparently escaping > with \, but I cannot find where.

here is the test repo.

Output:

2024/09/05 16:44:11 Rows: 75
2024/09/05 16:44:11 Rows: 0
2024/09/05 16:44:11 SQLRequest: -1:query failed with unrecognized token: "\"
Dominant language
Go
Stars
11
Forks
16
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ElementsProject/glightning

All issues in ElementsProject/glightning

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.