github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 19:52:56 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[PR #2326] [MERGED] ✨ allow running AQL against local database #4252

New Issue
Closed
opened 2026-02-28 20:53:41 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-02-28 20:53:41 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/2326
Author: @MatissJanis
Created: 2/3/2024
Status: ✅ Merged
Merged: 2/5/2024
Merged by: @MatissJanis

Base: master ← Head: matiss/local-queries

📝 Commits (3)

📊 Changes

2 files changed (+10 additions, -2 deletions)

View changed files

📝 packages/loot-core/src/server/main.ts (+4 -2)
➕ upcoming-release-notes/2326.md (+6 -0)

📄 Description

Allow running AQL against the local database.

Is this secure?

I think so (but please disagree if you think otherwise).

My argument for allowing this outside dev mode is:

  1. it's a pretty useful feature - especially for support when we need to get some data from the user;
  2. if an attacker gains access to window - he might as well have gotten access to the entire local database, so exposing this new query mechanism isn't really introducing a bigger vector of attack

Sample:

window
  .$query(window.$q('accounts').select('*'))
  .then(({ data }) => console.log(data));

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/actualbudget/actual/pull/2326 **Author:** [@MatissJanis](https://github.com/MatissJanis) **Created:** 2/3/2024 **Status:** ✅ Merged **Merged:** 2/5/2024 **Merged by:** [@MatissJanis](https://github.com/MatissJanis) **Base:** `master` ← **Head:** `matiss/local-queries` --- ### 📝 Commits (3) - [`5516ebd`](https://github.com/actualbudget/actual/commit/5516ebdd3f873cc71f7146fc5bbdcca639004265) :sparkles: allow running AQL against local database - [`65d8223`](https://github.com/actualbudget/actual/commit/65d822320058367028d88d5b39bc198b1a668d8f) Release notes - [`ff7a972`](https://github.com/actualbudget/actual/commit/ff7a9720b598c388905c6fb3acdd2ed5942d62e9) Release notes ### 📊 Changes **2 files changed** (+10 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `packages/loot-core/src/server/main.ts` (+4 -2) ➕ `upcoming-release-notes/2326.md` (+6 -0) </details> ### 📄 Description Allow running AQL against the local database. **Is this secure?** I think so (but please disagree if you think otherwise). My argument for allowing this outside dev mode is: 1. it's a pretty useful feature - especially for support when we need to get some data from the user; 2. if an attacker gains access to `window` - he might as well have gotten access to the entire local database, so exposing this new query mechanism isn't really introducing a bigger vector of attack --- Sample: ```javascript window .$query(window.$q('accounts').select('*')) .then(({ data }) => console.log(data)); ``` --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-02-28 20:53:41 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#4252
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?