firebase / firebase/firebase-admin-node
Realtime Database - reading data gives wrong value if transaction is pending
- Dominant language
- TypeScript
- Stars
- 1.7k
- Forks
- 419
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 16
Description
### [REQUIRED] Step 2: Describe your environment
* Operating System version: macOS 14.5 (23F79)
* Firebase SDK version: 12.2.0
* Firebase Product: database
* Node.js version: v20.13.0
* NPM version: v10.5.2
### [REQUIRED] Step 3: Describe the problem
If a transaction is pending for a node, it doesn't show up when reading data for the parent node with `.once("value", ...)`. I'm not sure if this is a bug or intended behavior.
#### Steps to reproduce:
For these examples, our database looks like this:
```json
{
"example_list": [
"a",
"b",
"c"
]
}
```
This code works as expected:
```js
let ref = admin.database().ref("example_list");
ref.once('value', (snap) => {
console.log(snap.val())
});
```
Logs: `[ 'a', 'b', 'c' ]`
This code does NOT work as expected:
```js
admin.database().ref("example_list/1").transaction((currentData) => {
return currentData;
});
let ref = admin.database().ref("example_list");
ref.once('value', (snap) => {
console.log(snap.val())
});
```
Logs: `[ 'a', <1 empty item>, 'c' ]`
Adding a transaction first, which seems like a no-op, actually causes the read to return a different result.
Contributor guide
Research direction
Start with the Node.js reproduction using admin.database().ref(...).transaction(...) followed by a parent ref.once('value', ...), and compare the returned array with and without the transaction. Read the Realtime Database transaction and read behavior to determine the intended result; done means the pending-transaction case is corrected or explicitly resolved as intended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100