Skip to content
Discussion options

You must be logged in to vote

Update in 2026: the virtual model path has been downgraded and is on the deprecation path, so it should not be the main recommendation for new usage anymore.

For new projects, please prefer the Go model + migration workflow:

go run . migrate

Use the virtual model only for existing installations that already depend on it. If you are building a new data table now, defining the model in Go keeps the schema, migration, tests, and agent-readable code path easier to maintain.

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by lwnmengjing
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants