Do we need dynamic middleware insted of craeteing tables at setup? #1123

New issue

Open

opened 2026-05-25 07:56:53 +00:00 by c24danli · 0 comments

c24danli commented

2026-05-25 07:56:53 +00:00

Collaborator

Currently we run a lot of extra code at each insert, extra string manipulation all the way to create table before we see that it already exists.
This was nessesarry to have it dynamic when we had all tables in the same db, but now when we have stacks we it could just be declared in the init file for that stack, reducing extra logic and making the code a lot easier to read.
BoundlessFlowCampus2K\middleware\middleware\Program.cs MAIN

BoundlessFlowCampus2K\middleware\middleware\Program.cs Create table

The table could just be created at setup in
BoundlessFlowCampus2K\DockerCompose\stacks\xxx\init_sql

Currently we run a lot of extra code at each insert, extra string manipulation all the way to create table before we see that it already exists. This was nessesarry to have it dynamic when we had all tables in the same db, but now when we have stacks we it could just be declared in the init file for that stack, reducing extra logic and making the code a lot easier to read. BoundlessFlowCampus2K\middleware\middleware\Program.cs MAIN ![image](/attachments/109ccff4-caad-4e85-86a4-7db855b55007) BoundlessFlowCampus2K\middleware\middleware\Program.cs Create table ![image](/attachments/2b9611bd-4991-4587-b828-da5b9b807bf1) ![image](/attachments/84942e73-6fe4-415a-8e76-ccaedb17a230) The table could just be created at setup in BoundlessFlowCampus2K\DockerCompose\stacks\xxx\init_sql ![image](/attachments/1e04d839-0e42-492d-b6e3-d260a1ba4b01)

image.png

50 KiB

image.png

78 KiB

image.png

74 KiB

image.png

57 KiB