firebase / firebase/firebase-admin-node
Realtime Database - reading data gives wrong value if transaction is pending
- 主要语言
- TypeScript
- 星标
- 1.7k
- 派生
- 419
- 平均合并
- 3 天 10 小时
- 30 天内合并 PR
- 16
描述
### [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.
贡献指南
调研方向
从使用 admin.database().ref(...).transaction(...) 的 Node.js 复现开始,随后执行 parent ref.once('value', ...),并比较有无事务时返回的数组。阅读 Realtime Database 的事务和读取行为,以确定预期结果;待事务的情况得到修复,或按照预期得到明确解决,即视为完成。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- javascript, node.js
- 领域
- database
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100