Skip to content

Conversation

@danji90
Copy link
Contributor

@danji90 danji90 commented Nov 6, 2025

No description provided.

@danji90 danji90 self-assigned this Nov 6, 2025
@danji90 danji90 added the enhancement New feature or request label Nov 6, 2025
@vercel
Copy link

vercel bot commented Nov 6, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
tree-app Ready Ready Preview Comment Nov 6, 2025 10:29am
tree-app-tg Ready Ready Preview Comment Nov 6, 2025 10:29am

Copy link
Member

@friedjoff friedjoff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@danji90 just an idea: we could add a column "profile" to the main "projections" table and also import profile-specific data into that table. This would avoid separate tables for each profile and maybe even support hybrid modes later on (query merged main and profile data). Not sure if it makes more sense than the current approach, I'll let you decide.

Otherwise LGTM!

FROM
'/data/profiles/vd/projections.csv' DELIMITER ';' CSV HEADER;

UPDATE vd_projections_import
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@danji90 maybe add this directly to the source data (CSV file) to make it more transparent. This seems quite hidden to me. Also applies to "flachgründig".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Development

Successfully merging this pull request may close these issues.

3 participants