| ▲ | hasyimibhar 3 hours ago | |
The homepage shows an example of an agent accidentally dropping a table. 1. This is such an insane example, I don't get why would you give agents write access to your production db in the first place. Are people really doing this? I don't even have production connection urls on my laptop. Any manual statements executed against the db must be treated as a war-room situation with at least another engineer reviewing your SQL before you execute it. 2. Dropping the table could have easily caused writes to fail. Most likely there is no way to recover these writes (especially if it's from user requests), so it could have lead to loss of data. Reversing the table drop doesn't fix this issue. | ||
| ▲ | traceroute66 42 minutes ago | parent [-] | |
> Reversing the table drop doesn't fix this issue. Also reversing a table drop doesn't solve extra corruption routes such as cross-table dependencies. | ||