It says saved and there is no row in the database

The most confusing failure of the set, because everything reports success.

Seen in apps built with Lovable.

What is actually happening

A browser app talks to the database directly, and the database decides for itself what that visitor is allowed to do. When a rule refuses a write, the refusal can arrive as an ordinary response rather than as an error.

If the code does not inspect that response — and generated code frequently does not — the interface shows success, because nothing threw.

We can measure how many projects keep their schema in the repository: 24 of 100 do. For the remaining 76 the rules exist only inside a panel, and no amount of reading the code will tell you what they say.

Fixing it yourself

• Look at the response your save actually returns, rather than at whether it threw an exception.
• Then read the rules for that table in your database provider's panel, as the role a visitor has rather than as yourself.

Where it stops being a small job

Almost immediately. Rules that decide who may read and write depend on what your application means — which user owns which record, who may see what. That cannot be generated from the code, and it is the one part of this list we would not attempt without understanding what the app is for.