bvandeusen
6959e1220c
This reverts 2529b51. Not a retreat — a reordering, on the operator's
call, and the better sequence.
The squash's acceptance test (run 4971) found ~130 places where the ORM
models do not describe the deployed schema (#3275), including a
unique=True the database never had and two UNIQUE indexes that exist
only in migrations. Collapsing now would have baked all of that into the
one file a public installer starts from.
So: fix the drift first as ordinary migrations on the intact chain, let
the operator deploy so their database moves to the corrected head, and
only then collapse. The baseline is then generated from reconciled
models and reproduces a schema worth reproducing.
Nothing is lost by reverting. The baseline was never deployed, and
regenerating it after the fixes is strictly better than patching this
copy — it will come out of autogenerate correct rather than needing the
same hand-finishing twice.
33 lines
886 B
Python
33 lines
886 B
Python
import pytest
|
|
from sqlalchemy import select
|
|
|
|
from backend.app.models import AppSetting
|
|
|
|
pytestmark = pytest.mark.integration
|
|
|
|
|
|
@pytest.mark.asyncio
|
|
async def test_app_setting_table_round_trip(db):
|
|
db.add(AppSetting(key="extension_api_key", value="abc123"))
|
|
await db.flush()
|
|
row = (await db.execute(
|
|
select(AppSetting).where(AppSetting.key == "extension_api_key")
|
|
)).scalar_one()
|
|
assert row.value == "abc123"
|
|
assert row.updated_at is not None
|
|
|
|
|
|
@pytest.mark.asyncio
|
|
async def test_app_setting_upsert(db):
|
|
db.add(AppSetting(key="k", value="v1"))
|
|
await db.flush()
|
|
row = (await db.execute(
|
|
select(AppSetting).where(AppSetting.key == "k")
|
|
)).scalar_one()
|
|
row.value = "v2"
|
|
await db.flush()
|
|
again = (await db.execute(
|
|
select(AppSetting.value).where(AppSetting.key == "k")
|
|
)).scalar_one()
|
|
assert again == "v2"
|