Category: VacationRelay
-
VaRe&DaIn–part 040 of n–DatabaseIndependence
Now comes the real part. I want the app to work with any database—SQLite, PostgreSQL, SQL Server, and MongoDB—and to choose the database type and connection string at startup. In the .NET world, I see two main options: 1. The plain SQL-style approach: I define an interface with methods for the data I need in…
-
VaRe&DaIn–part 030 of n–multi database testing
Once every database backend (SQLite, SQL Server, PostgreSQL, MongoDB) could create its own schema at Aspire startup, I had a new problem: proving it, for all four providers, not just one, without writing four unrelated test suites by hand. My solution was to combine a single AppHost wiring pattern with one shared Playwright verification helper…
-
VaRe&DaIn–part 020 of n–testing sqlite has 2 tables
Once the schema creation script ran at startup, I needed proof — not just trust — that SQLite really ends up with the two tables: `vr_data` and `vr_data_history`. So I wrote a Playwright UI test that drives SqliteWeb (the viewer exposed by Aspire) and asserts both tables are visible and that `vr_data` has the expected…
-
VaRe&DaIn–part 001 of n – start idea
I wanted a proof-of-concept app that is truly database-independent: SQL Server, PostgreSQL, MongoDB, or just a local SQLite file. Partly for fun, partly for the engineering challenge, and mostly because real enterprise installs rarely have the same infrastructure. That is the **DaIn (Database Independence)** goal behind this project. That idea became **Vacation Relay (VaRe)**: when…
-
VaRe&DaIn–part 010 of n–creation of database.md
The first iteration of the project should create the database – no matter if SqlServer, PostgreSql, Sqlite or MongoDB ( see references ) . Database independence sounds simple until,because I use simple connections, the app should do schema creation. The challenge is that each backend speaks a different language. SQL Server and PostgreSQL need SQL…